<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:16:33 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-1558] Auto Ordering of Requests Queue Based on Type (i.e. Recalls Filled Before Holds)</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-1558</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;FOLIO has several different request types so far: page, recall and hold.  Currently, the request queue is ordered first-in-first-out (FIFO).  This means that a hold request (&quot;I&apos;d like this when it&apos;s available&quot;) could be higher in the queue than a recall requests (&quot;I need this as soon as possible&quot;).  This is not going to work for (most) institutions that plan to use both recalls and holds.&lt;/p&gt;

&lt;p&gt;We do plan to implement the ability to &lt;em&gt;manually&lt;/em&gt; re-order the request queue (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1242&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1242&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Manually Reorder Request Queue (Dedicated Request Queue Page with Re-Order Capabilities)&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-1242
        &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;
) but the system should also do sensible auto-ordering, as manual reordering requires that staff is aware that re-ordering is needed (and this may not be obvious, especially if the requests are patron-generated).  The scope of this feature is implementing the sensible auto-ordering of recalls above holds.&lt;/p&gt;

&lt;p&gt;NOTE 1: This feature is only necessary when there are both recalls and holds in a request queue for a single item (with a hold above a recall).  If your institution doesn&apos;t expect to be in this situation (because you only use recalls or holds OR because it&apos;s rare to have both recalls and holds on a single item, you might not rank this high).&lt;/p&gt;

&lt;p&gt;NOTE 2: I tested how FOLIO works without this feature implemented and here&apos;s what happens if a recall is made for a loaned item which already has a hold request on it:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;The due date for the current loan will change according to the recall settings in the loan policy even though the recall is not at the top of the request queue&lt;/li&gt;
	&lt;li&gt;A patron notice will be triggered (assuming one has been set up) to let the current borrower know their item has been recalled&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;So, under normal circumstances, the current borrower will get the recall notice and return the item quickly at which point it will be checked in and the hold request will begin fulfillment (since it&apos;s first in the queue).  When that requester picks the item up, the loan period for the new loan will be shortened if the applied loan policy has made use of the &quot;minimum guaranteed loan period for recalled items&quot;.  When the item is subsequently returned, it will be checked in and the recall request will begin fulfillment.&lt;/p&gt;

&lt;p&gt;-------------------------------------------------------------------------&lt;br/&gt;
Details (from &lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/RA/2019-2-11+Resource+Access+Meeting+Notes&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;SIG meeting&lt;/a&gt;):&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Recall and hold requests can exist together in the request queue for an item&lt;/li&gt;
	&lt;li&gt;Recall requests should automatically be prioritized over holds in the requests queue so that the requests that were identified as recalls (meaning &quot;I need this right away&quot;) take priority over those identified as holds (&quot;I&apos;d like this when it&apos;s available&quot;)&lt;/li&gt;
	&lt;li&gt;If a request is awaiting pickup, nothing should be able to jump it in the queue (because a notification has already gone out to the requester)&lt;/li&gt;
	&lt;li&gt;Page requests are only created for items that have no other requests on them.  It is possible to put a hold on an item that has been paged, but there is no need for the system to prioritize holds over pages or vice versa&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;For more info on the differences between request types, see this document: &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1jaID-HGft3q4YzJq6Ycy2ejWByAIvou3Zyyw4ko87YI/edit#gid=0&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1jaID-HGft3q4YzJq6Ycy2ejWByAIvou3Zyyw4ko87YI/edit#gid=0&lt;/a&gt; &lt;/p&gt;</description>
                <environment></environment>
        <key id="13082">UXPROD-1558</key>
            <summary>Auto Ordering of Requests Queue Based on Type (i.e. Recalls Filled Before Holds)</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="10049">UXPROD-790</parent>
                                    <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="10000" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/generic.png" description="(Migrated on 4 Feb 2024 13:41 UTC)">Draft</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="5af5ed55244bc90a106063c7">Cate Boerema</reporter>
                                    <labels>
                            <label>requests</label>
                            <label>round_iv</label>
                            <label>swag</label>
                    </labels>
                <created>Mon, 4 Mar 2019 15:22:10 +0000</created>
                <updated>Tue, 10 Jan 2023 16:37:59 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="16502" author="5afc1ced2083b15a0bd3e494" created="Tue, 5 Mar 2019 09:51:59 +0000"  >&lt;p&gt;We do not plan to implement the &quot;holds&quot; type of request, and so are unsure of whether this is really relevant to us. Do you agree, &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;/p&gt;</comment>
                                                            <comment id="16504" author="5af5ed55244bc90a106063c7" created="Tue, 5 Mar 2019 10:01:10 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5afc1ced2083b15a0bd3e494&quot; class=&quot;user-hover&quot; rel=&quot;5afc1ced2083b15a0bd3e494&quot; data-account-id=&quot;5afc1ced2083b15a0bd3e494&quot; accountid=&quot;5afc1ced2083b15a0bd3e494&quot; rel=&quot;noreferrer&quot;&gt;Lisa Sj&#246;gren&lt;/a&gt;.  Correct, since you guys aren&apos;t using Holds, you will not need this.  This is really only relevant for institutions that plan to use both recalls and holds.&lt;/p&gt;</comment>
                                                            <comment id="16507" author="5afc1ced2083b15a0bd3e494" created="Wed, 6 Mar 2019 08:26:33 +0000"  >&lt;p&gt;Great! Thanks for clarifying, &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;/p&gt;</comment>
                                                            <comment id="16510" author="5c48911b54e1e6466b11f38c" created="Fri, 28 Jun 2019 16:29:48 +0000"  >&lt;p&gt;Duke has marked this as Go-Live; if it ends up slipping and isn&apos;t available, we absolutely need manual ordering (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1242&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1242&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Manually Reorder Request Queue (Dedicated Request Queue Page with Re-Order Capabilities)&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-1242
        &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;
) to go live.&lt;/p&gt;</comment>
                                                            <comment id="16513" author="5af5ed55244bc90a106063c7" created="Tue, 2 Jul 2019 10:11:24 +0000"  >&lt;p&gt;Discussed in RA SIG re-ranking meeting.  You can find the discussion starting at 19:33 in this recording: &lt;a href=&quot;https://drive.google.com/file/d/15RbACU90Ln4JAazWSz0iM4ZSYia6mIaK/view?usp=sharing&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://drive.google.com/file/d/15RbACU90Ln4JAazWSz0iM4ZSYia6mIaK/view?usp=sharing&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I had thought this was ranked surprisingly low and wanted to double check people understood that, without this feature, a hold could be higher in the queue than a recall which is contrary to the definition of the request types (recall = get me this asap while hold = i&apos;ll take it when available).  Most on the call felt they could actually live without this feature because of low utilization of both hold types (recall and hold) simultaneously on a single item.  &lt;/p&gt;

&lt;p&gt;Notes:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;One potential workaround, once we have implemented 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1242&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1242&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Manually Reorder Request Queue (Dedicated Request Queue Page with Re-Order Capabilities)&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-1242
        &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;
, would be to require staff to &lt;em&gt;manually&lt;/em&gt; reorder the queue so recalls are above holds.  This isn&apos;t an ideal solution because there is no obvious way to know that a queue needs reordering.&lt;/li&gt;
	&lt;li&gt;We need to make sure that, without this feature, things are not, essentially broken.  Some questions that come to mind that need testing:
	&lt;ol&gt;
		&lt;li&gt;What happens/should happen when a recall is placed after a hold request?  Is the due date of the current loan shortened?  Is a notice sent to the current borrower?  Since this is apparently an edge case, it might not matter too much if the answer to these questions is yes or no, but they should be both yes or both no.  Cate will test.&lt;/li&gt;
	&lt;/ol&gt;
	&lt;/li&gt;
&lt;/ol&gt;
</comment>
                                                            <comment id="16516" author="5af5ed55244bc90a106063c7" created="Wed, 3 Jul 2019 14:27:06 +0000"  >&lt;p&gt;Okay, I tested and here&apos;s what happens if a recall is made for a loaned item which already has a hold request on it:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The due date for the current loan will change according to the recall settings in the loan policy even though the recall is not at the top of the request queue&lt;/li&gt;
	&lt;li&gt;A patron notice will be triggered (assuming one has been set up) to let the current borrower know their item has been recalled&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;So, under normal circumstances, the current borrower will get the recall notice and return the item quickly at which point it will be checked in and the hold request will begin fulfillment (since it&apos;s first in the queue).  When that requester picks the item up, the loan period for the new loan will be shortened if the applied loan policy has made use of the &quot;minimum guaranteed loan period for recalled items&quot;.  When the item is subsequently returned, it will be checked in and the recall request will begin fulfillment.&lt;/p&gt;

&lt;p&gt;I will add this info to the feature summary, as it will be relevant for ranking.&lt;/p&gt;</comment>
                                                            <comment id="16520" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Mon, 7 Mar 2022 19:32:30 +0000"  >&lt;p&gt;This feature is marked DRAFT until &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=632e148361dbef2805be710f&quot; class=&quot;user-hover&quot; rel=&quot;632e148361dbef2805be710f&quot; data-account-id=&quot;632e148361dbef2805be710f&quot; accountid=&quot;632e148361dbef2805be710f&quot; rel=&quot;noreferrer&quot;&gt;Brooks Travis&lt;/a&gt; has a chance to review it for validity.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="46962">CIRC-278</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10734">UXPROD-1242</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="10123"><![CDATA[XL < 15 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10054" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Back End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5af5ed55244bc90a106063c7</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)">Requests</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Estimation Notes and Assumptions</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CB: Per discussion with the cap planning team, some of use non-developers are estimating features to avoid disrupting development.  I will tag this as &amp;quot;swag&amp;quot; so we know to come back and revisit later when we have more info and are  closer to development.</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>5af5ed55244bc90a106063c7</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front-End Confidence factor</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10107"><![CDATA[Low]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>29.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10064" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>PO Ranking Note</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.&lt;br/&gt;
2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10045" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Potential Workaround</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Cate Boerema: Discussed with SIG one potential workaround, once we have implemented &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1242&quot; title=&quot;Manually Reorder Request Queue (Dedicated Request Queue Page with Re-Order Capabilities)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;UXPROD-1242&quot;&gt;&lt;strike&gt;UXPROD-1242&lt;/strike&gt;&lt;/a&gt;, would be to require staff to manually reorder the queue so recalls are above holds. This isn&amp;#39;t an ideal solution because there is no obvious way to know that a queue needs reordering.</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzzhef:</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="10226"><![CDATA[R4]]></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="10216"><![CDATA[R4]]></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="10236"><![CDATA[R4]]></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="10241"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10075" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Grand Valley (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10246"><![CDATA[R4]]></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="10256"><![CDATA[R4]]></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="10261"><![CDATA[R4]]></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="10297"><![CDATA[R4]]></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="10327"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10076" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: hbz (TBD)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10251"><![CDATA[R4]]></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>Tue, 5 Mar 2019 09:51:59 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                </customfields>
    </item>
</channel>
</rss>