<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:14:16 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[UXPROD-1280] Paging Requests Individual Staff Slip</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1280</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;&lt;b&gt;Purpose/Problem:&lt;/b&gt;&lt;br/&gt;
Paging requests are requests on items that are available in the library.  To fulfill these types of requests, library staff need to print the list of open paging requests and go get the items off the shelf.  Many institutions print a single report for this purpose (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1138&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1138&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Requests Pick List: CSV Export&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-1138
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and  
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-923&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-923&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Requests in-app report: Requests Pick List&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-923
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Draft&lt;/span&gt;
            &lt;/span&gt;
) but some want the option to print individual slips instead. &lt;b&gt;NOTE: The report might be an acceptable work-around temporarily until this feature can be developed.&lt;/b&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Some libraries use an individual pick slip for retrieving an item from (closed) stacks and then place the same slip in the item on the collection shelf. The top printed line on the slip could provide a (pseudonymous) identification of the patron, that could stick out at the top for easy collection. The pick slip also serves as a paging slip in this case.&lt;/li&gt;
	&lt;li&gt;Large closed stack libraries (Magazinbibliotheken) might want to aggregate pick slips for a certain period of time, sort them by call number and print them in a batch. This would provide one way of optimizing collection routes for staff.&lt;/li&gt;
	&lt;li&gt;Other libraries want to have these slips print as a request comes in.&lt;/li&gt;
	&lt;li&gt;Closed stack libraries might leave a copy of the loaned item call slip in the stack until the item is returned. This would require the system to print each call slip twice.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;b&gt;Implementation Thoughts:&lt;/b&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Setting to enable this option&lt;/li&gt;
	&lt;li&gt;Ability to CRUD the paging slip template, specifically the content and format (like hold slips)&lt;/li&gt;
	&lt;li&gt;Ability to print individual paging slips on demand and/or on a schedule&lt;/li&gt;
	&lt;li&gt;Ability to print only slips relevant to your location&lt;/li&gt;
	&lt;li&gt;Individual slips are properly sorted and collated (by location, call number, maybe even custom field - sort order should be configurable)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Further use cases:&lt;/b&gt; (from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5e8c99cbf135980b7bd6d120&quot; class=&quot;user-hover&quot; rel=&quot;5e8c99cbf135980b7bd6d120&quot; data-account-id=&quot;5e8c99cbf135980b7bd6d120&quot; accountid=&quot;5e8c99cbf135980b7bd6d120&quot; rel=&quot;noreferrer&quot;&gt;Uschi Klute&lt;/a&gt; in comments below)&lt;br/&gt;
In our larger libraries there are several closed stacks, each with its own printer. The slips automatically printed there belong to exactly this closed stacks area. In most libraries the books are picked &quot;on demand&quot; and not with a certain provision time. &lt;br/&gt;
If an unexpectedly large amount of slips has been produced on a printer, it can easily be divided between two employees.&lt;br/&gt;
For media which were not found in the shelf, a corresponding text can be noted on the slip. Those slips are collected at the service point and checked again at a later time.&lt;br/&gt;
If the books are then transported to the service point, it is important that the request slip is in the book, as this is the only way for everyone involved to recognize that it is an ordered and already picked book.&lt;br/&gt;
With a list, the status of the book (already picked or not found etc.) would have to be noted on the (paper) list.&lt;br/&gt;
A list is very impractical and would cause much more work.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10828">UXPROD-1280</key>
            <summary>Paging Requests Individual Staff Slip</summary>
                <type id="10002" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium">New Feature</type>
                            <parent id="13681">UXPROD-19</parent>
                                    <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a">Darcy Branchini</assignee>
                                                                <reporter accountid="5af5ed55244bc90a106063c7">Cate Boerema</reporter>
                                    <labels>
                            <label>cap-mvp</label>
                            <label>po-mvp</label>
                            <label>printslips</label>
                            <label>q4-2019-at-risk</label>
                            <label>requests</label>
                    </labels>
                <created>Mon, 5 Nov 2018 13:10:57 +0000</created>
                <updated>Wed, 16 Sep 2020 21:12:29 +0000</updated>
                            <resolved>Tue, 10 Dec 2019 21:07:38 +0000</resolved>
                                                    <fixVersion>Q4 2019</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                                                            <comment id="13711" author="5af5ed55244bc90a106063c7" created="Mon, 5 Nov 2018 13:11:43 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A20eef5db-dfe5-49a6-a9b3-cd32cb09b0f1&quot; class=&quot;user-hover&quot; rel=&quot;712020:20eef5db-dfe5-49a6-a9b3-cd32cb09b0f1&quot; data-account-id=&quot;712020:20eef5db-dfe5-49a6-a9b3-cd32cb09b0f1&quot; accountid=&quot;712020:20eef5db-dfe5-49a6-a9b3-cd32cb09b0f1&quot; rel=&quot;noreferrer&quot;&gt;Schwill, Carsten&lt;/a&gt;, can you please take a look at this feature and add any additions/changes?&lt;/p&gt;</comment>
                                                            <comment id="13713" author="712020:20eef5db-dfe5-49a6-a9b3-cd32cb09b0f1" created="Thu, 8 Nov 2018 12:44:41 +0000"  >&lt;ol&gt;
	&lt;li&gt;Some libraries use an individual pick slip for retrieving an item from (closed) stacks and then place the same slip in the item on the collection shelf. The top printed line on the slip could provide a (pseudonymous) identification of the patron, that could stick out at the top for easy collection. The pick slip also serves as a paging slip in this case.&lt;/li&gt;
	&lt;li&gt;Large closed stack libraries (Magazinbibliotheken) might want to aggregate pick slips for a certain period of time, sort them by call number and print them in a batch. This would provide one way of optimizing collection routes for staff.&lt;/li&gt;
	&lt;li&gt;Closed stack libraries might leave a copy of the loaned item call slip in the stack until the item is returned. This would require the system to print each call slip twice.&lt;/li&gt;
&lt;/ol&gt;
</comment>
                                                            <comment id="13715" author="5af5ed55244bc90a106063c7" created="Wed, 15 May 2019 16:23:51 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A925f55a1-465f-4875-8818-49cbe9a45838&quot; class=&quot;user-hover&quot; rel=&quot;557058:925f55a1-465f-4875-8818-49cbe9a45838&quot; data-account-id=&quot;557058:925f55a1-465f-4875-8818-49cbe9a45838&quot; accountid=&quot;557058:925f55a1-465f-4875-8818-49cbe9a45838&quot; rel=&quot;noreferrer&quot;&gt;Kostyantyn Khodarev&lt;/a&gt; could you please provide the t-shirt size estimates for this feature?  I feel like Vega would be best positioned to estimate this since it&apos;s a kind of staff slip (like hold and transit).  These estimates are intended to be rough - please don&apos;t spend too much time thinking about it.  That said, if you have questions, please let me know.&lt;/p&gt;

&lt;p&gt;+ &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; class=&quot;user-hover&quot; rel=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; data-account-id=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; accountid=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; rel=&quot;noreferrer&quot;&gt;Darcy Branchini&lt;/a&gt; because this one actually falls between our areas.  Not sure if this should be considered part of Requests or Staff slips...  Anyway, we need it estimated regardless &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="13716" author="557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a" created="Thu, 16 May 2019 14:05:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; - My understanding is that from a user perspective, this is closely related to 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-923&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-923&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Requests in-app report: Requests Pick List&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-923
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Draft&lt;/span&gt;
            &lt;/span&gt;
. It supports the same workflow function &amp;#8211; staff retrieving requested items off of shelves. And it&apos;s a matter of preference by institution and/or maybe library or service point, some prefer to have one list with all outstanding picks and others prefer to have individual items printed on separate sheets/slips. I do wonder if both are necessary in FOLIO. Since items will be scanned at the service point after they are retrieved and hold slips can (or will) be printed, then do they need individual pick slips? Also, perhaps their current systems didn&apos;t allow them to do one consolidated list by location so that is why they do this? Also, I know some were using pick slips as hold slips, so they didn&apos;t have to print another slip. These are all good questions to get clarification on from the SIG.&lt;/p&gt;</comment>
                                                            <comment id="13718" author="5e8c99cbf135980b7bd6d120" created="Tue, 11 Jun 2019 07:10:53 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; class=&quot;user-hover&quot; rel=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; data-account-id=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; accountid=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; rel=&quot;noreferrer&quot;&gt;Darcy Branchini&lt;/a&gt; - It is absolutely necessary that individual slips are created for page requests.&lt;br/&gt;
In our larger libraries there are several closed stacks, each with its own printer. The slips automatically printed there belong to exactly this closed stacks area. In most libraries the books are picked &quot;on demand&quot; and not with a certain provision time. &lt;br/&gt;
If an unexpectedly large amount of slips has been produced on a printer, it can easily be divided between two employees.&lt;br/&gt;
For media which were not found in the shelf, a corresponding text can be noted on the slip. Those slips are collected at the service point and checked again at a later time.&lt;br/&gt;
If the books are then transported to the service point, it is important that the request slip is in the book, as this is the only way for everyone involved to recognize that it is an ordered and already picked book.&lt;br/&gt;
With a list, the status of the book (already picked or not found etc.) would have to be noted on the (paper) list.&lt;br/&gt;
A list is very impractical and would cause much more work.&lt;/p&gt;</comment>
                                                            <comment id="13720" author="5d6eeadef989e00d8c7e897b" created="Tue, 11 Jun 2019 15:40:52 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; the capacity plan has this as a planned release as q2 2020 and this is q4 2019 - which one is correct?&lt;/p&gt;
</comment>
                                                            <comment id="13722" author="5af5ed55244bc90a106063c7" created="Wed, 12 Jun 2019 08:49:38 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5d6eeadef989e00d8c7e897b&quot; class=&quot;user-hover&quot; rel=&quot;5d6eeadef989e00d8c7e897b&quot; data-account-id=&quot;5d6eeadef989e00d8c7e897b&quot; accountid=&quot;5d6eeadef989e00d8c7e897b&quot; rel=&quot;noreferrer&quot;&gt;Anya&lt;/a&gt; target releases beyond Q2 should be ignored.  We haven&apos;t completed planning for Q3 and beyond.  The dates you see are just POs&apos; best guesses and many of them are very stale&lt;/p&gt;</comment>
                                                            <comment id="13724" author="557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a" created="Wed, 12 Jun 2019 18:12:11 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, I was planning to handle this as the PO for &quot;staff or print slips,&quot; but are you planning to instead?&lt;/p&gt;</comment>
                                                            <comment id="13726" author="5af5ed55244bc90a106063c7" created="Thu, 13 Jun 2019 10:12:49 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; class=&quot;user-hover&quot; rel=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; data-account-id=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; accountid=&quot;557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a&quot; rel=&quot;noreferrer&quot;&gt;Darcy Branchini&lt;/a&gt; this one could go either way as it&apos;s definitely a staff slip and definitely request-related.  As I mentioned earlier, now that the basic staff slip feature is in place, I feel that other POs should be able to extend on it, as long as they keep you in the loop.  That said, I&apos;m time-starved and more than happy to let you take this one.  &lt;/p&gt;</comment>
                                                            <comment id="13727" author="557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a" created="Thu, 13 Jun 2019 13:07:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, since I was already planning to, I&apos;ll continue with that plan.&lt;/p&gt;</comment>
                                                            <comment id="13729" author="5af5ed55244bc90a106063c7" created="Fri, 28 Jun 2019 10:51:09 +0000"  >&lt;p&gt;Tentatively reassigning to Vega, since that&apos;s the team Darcy works with most and they &quot;own&quot; staff slips&lt;/p&gt;</comment>
                                                            <comment id="13730" author="557058:ad89644f-caaa-466a-8bf5-cdcd4358fa9a" created="Tue, 2 Jul 2019 19:40:51 +0000"  >&lt;p&gt;This feature was reviewed at the RA SIG meeting on 7/1/2019 and consensus was that this was still a go-live feature. However, many institutions felt the workaround proposed above (using the report instead of individual slips) might be an acceptable work-around temporarily. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="48192">CIRC-494</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="48187">CIRC-504</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="25936">UIREQ-382</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10270">UXPROD-272</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10807">UXPROD-1138</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13057">UXPROD-923</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10122"><![CDATA[Large < 10 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10054" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Back End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:925f55a1-465f-4875-8818-49cbe9a45838</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10187"><![CDATA[Vega]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Staff Slips</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10098"><![CDATA[Large < 10 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10051" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Front End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:925f55a1-465f-4875-8818-49cbe9a45838</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>91.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10045" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Potential Workaround</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Darcy &lt;br/&gt;
- &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-923&quot; title=&quot;Requests in-app report: Requests Pick List&quot; class=&quot;issue-link&quot; data-issue-key=&quot;UXPROD-923&quot;&gt;UXPROD-923&lt;/a&gt; Requests in-app report: Requests Pick List, but that feature also tags this feature as a possible work-around. I&amp;#39;m ranking it higher assuming this one will be implemented and &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-923&quot; title=&quot;Requests in-app report: Requests Pick List&quot; class=&quot;issue-link&quot; data-issue-key=&quot;UXPROD-923&quot;&gt;UXPROD-923&lt;/a&gt; will not.</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzy83w:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10071" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: 5Colleges (Full Jul 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10223"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10067" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chalmers (Impl Aut 2019)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10207"><![CDATA[R5]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10068" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chicago (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10211"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10069" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Cornell (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10214"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10070" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Duke (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10218"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10073" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: FLO (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10233"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10074" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: GBV (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10239"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10077" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Hungary (MVP End 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10253"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10078" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Lehigh (MVP Summer 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10259"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10079" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Leipzig (Full TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10263"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10085" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: MO State (MVP June 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10295"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10089" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: TAMU (MVP Jan 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10314"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10091" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: U of AL (MVP Oct 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10324"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10076" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: hbz (TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10248"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 8 Nov 2018 12:44:41 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>