<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:07:49 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-393] Finalize display format of Call Number within Fees/Fines</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-393</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;SIG needs to see a call number field that includes more than just the call number.  They want to see the year, volume number, copy number, etc. (see examples on attached mock-up).  We will need a component that creates the call number field.  This component will then be used by any app that needs to present a more descriptive call number.  &lt;/p&gt;

&lt;p&gt;Notes from previous discussions:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;This call number field needs to be sortable&lt;/li&gt;
	&lt;li&gt;Talk to &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3Abe36acda-040d-4925-b3df-ebd7e16d4b5b&quot; class=&quot;user-hover&quot; rel=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; data-account-id=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; accountid=&quot;70121:be36acda-040d-4925-b3df-ebd7e16d4b5b&quot; rel=&quot;noreferrer&quot;&gt;lew235&lt;/a&gt; about building the call number&lt;/li&gt;
	&lt;li&gt;See the Inventory Beta Metadata Elements which is the resent version, and will be implemented by Q4 2018: &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=139536469&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=139536469&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;Also see the Holdings Table&lt;/li&gt;
	&lt;li&gt;Meet with David, Andrea, Tania, Laura, and Charlotte&lt;/li&gt;
&lt;/ul&gt;

</description>
                <environment></environment>
        <key id="10442">UXPROD-393</key>
            <summary>Finalize display format of Call Number within Fees/Fines</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="13654">UXPROD-792</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:a957226f-df85-4fc8-97f4-8b27a26029ed">Holly Mistlebauer</assignee>
                                                                <reporter accountid="557058:a957226f-df85-4fc8-97f4-8b27a26029ed">Holly Mistlebauer</reporter>
                                    <labels>
                            <label>UNAM</label>
                            <label>cap-mvp</label>
                            <label>feesfines</label>
                            <label>po-mvp</label>
                            <label>q4-2019-at-risk</label>
                            <label>q4-2019-spillover</label>
                            <label>resourceaccess</label>
                    </labels>
                <created>Thu, 22 Mar 2018 19:29:59 +0000</created>
                <updated>Tue, 12 Jul 2022 18:39:07 +0000</updated>
                            <resolved>Tue, 12 Jul 2022 18:39:07 +0000</resolved>
                                                    <fixVersion>Morning Glory (R2 2022)</fixVersion>
                                    <component>Fees/Fines</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                    <timespent seconds="900">15 minutes</timespent>
                                <comments>
                                                            <comment id="12929" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Thu, 22 Mar 2018 19:47:41 +0000"  >&lt;p&gt;Cate added an item on the RA SIG Parking Lot called &quot;Normalize Call Number.&quot;  The description says...&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Need a normalized call number stored and used for sorting on Loans page. We are currently displaying a concatenated call number on the Loans page to save on real-estate. But sorting by this concatenated string isn&apos;t going to work. FOLIO needs to store a &quot;normalized&quot;call # and use that for sorting on Loans and elsewhere. From experience, this data really needs to be stored as opposed to generated on-the-fly. This is a must-have for v1.&lt;/em&gt;&lt;/p&gt;</comment>
                                                            <comment id="12931" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Fri, 6 Apr 2018 19:42:14 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt; - this story links to the wikipage with the list started by Kathryn Harnish, but there is a more updated master spreadsheet for all Metadata elements implemented in Inventory (Instance, Holdings, Item records) covering both the implemented elements (alpha), and already identified &apos;missing elements&apos; which we are working on to be implemented (beta) - see: &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Following elements related to Call Numbers have been implemented/identified for the Holdings record&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Call Number (implemented - alpha)&lt;/li&gt;
	&lt;li&gt;Call Number Prefix (identified)&lt;/li&gt;
	&lt;li&gt;Call Number Type (identified)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="12935" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 2 Oct 2018 11:24:37 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt; - I have added some update info to this UXPROD feature:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;link to the Inventory Beta Metadata element spreadsheet - in the description&lt;/li&gt;
	&lt;li&gt;and spec of call numbers (holdings record, and item record) - see: attachments&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="12938" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Thu, 17 Jan 2019 18:53:20 +0000"  >&lt;p&gt;The fields that make up the displayed call number are...&lt;/p&gt;

&lt;p&gt;Call number prefix&lt;br/&gt;
Call number&lt;br/&gt;
Call number suffix&lt;br/&gt;
Copy number&lt;/p&gt;

&lt;p&gt;Enumeration&lt;br/&gt;
Volume&lt;br/&gt;
Chronology&lt;br/&gt;
Year, Caption (although there were questions about this field being a combined field&#8230; perhaps it should just be labeled Caption and that might include year data, if desired?)&lt;/p&gt;
</comment>
                                                            <comment id="12940" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Fri, 18 Jan 2019 19:23:02 +0000"  >&lt;p&gt;At the 1/17 RA SIG meeting it was decided that each tenet should be able to build the call number in the format they want for the call slips.  Despite this, we are going to attempt to build a shared format for display within fees/fines and loans.  Adding a setting for doing this would be a lot of extra work.  Another related issue is the sorting of the call number.  The call number needs to be sorted on both Fees/Fines History and Loans History.  Holly will meet with the CUL IT expert on this topic to gather some info on this.&lt;/p&gt;</comment>
                                                            <comment id="12942" author="5d6eeadef989e00d8c7e897b" created="Fri, 29 Mar 2019 22:42:21 +0000"  >&lt;p&gt;Comment from the March Meeting : call number sort needs to work&lt;/p&gt;</comment>
                                                            <comment id="12944" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Mon, 14 Oct 2019 14:57:44 +0000"  >&lt;p&gt;Per Laura Wright...&lt;/p&gt;

&lt;p&gt;&amp;lt;prefix&amp;gt; &amp;lt;call number&amp;gt; &amp;lt;suffix&amp;gt; &amp;lt;enumeration&amp;gt; &amp;lt;chronology&amp;gt; &amp;lt;volume&amp;gt; &amp;lt;copy number&amp;gt;&lt;/p&gt;

&lt;p&gt;Using real field names (note that there is a space between each field)...&lt;br/&gt;
&amp;lt;Call number prefix&amp;gt; &amp;lt;Call number&amp;gt; &amp;lt;Call number suffix&amp;gt; &amp;lt;Enumeration&amp;gt; &amp;lt;Chronology&amp;gt; &amp;lt;Volume&amp;gt; &amp;lt;Copy number&amp;gt;&lt;/p&gt;

&lt;p&gt;All data is available via the &lt;b&gt;ITEM RECORD&lt;/b&gt; (see attached file &lt;font color=&quot;#d04437&quot;&gt;ItemRecord.png&lt;/font&gt;)...&lt;/p&gt;

&lt;p&gt;&lt;b&gt;ITEM DATA&lt;/b&gt;&lt;br/&gt;
Call number prefix&lt;br/&gt;
Call number&lt;br/&gt;
Call number suffix&lt;br/&gt;
Copy number&lt;/p&gt;

&lt;p&gt;&lt;b&gt;ENUMERATION&lt;/b&gt;&lt;br/&gt;
Volume&lt;br/&gt;
Enumeration&lt;br/&gt;
Chronology&lt;/p&gt;
</comment>
                                                            <comment id="12946" author="5af5ed55244bc90a106063c7" created="Thu, 24 Oct 2019 09:33:59 +0000"  >&lt;p&gt;Hi Holly.  I cleaned up the links between features a bit:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Since this is about call number display, the feature that blocks it is actually Implementing effective call number: 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1626&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1626&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Store Effective Call Number Prefix, Call Number and Suffix in the Item Record&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-1626
        &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;
 (not Implementing normalized call number for sorting  
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2002&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2002&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement Normalized Call Number for Sorting (LoC Parsing Only)&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-2002
        &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;
)&lt;/li&gt;
	&lt;li&gt;To that point, I think it&apos;s really important that, when your stories refer to the data elements to include when building the call number, they need to refer to &amp;lt;Effective Call Number Prefix&amp;gt; &amp;lt;Effective Call Number&amp;gt; &amp;lt;Effective Call Number Suffix&amp;gt; &amp;lt;Enumeration&amp;gt; &amp;lt;Chronology&amp;gt; &amp;lt;Volume&amp;gt; &amp;lt;Effective Copy Number&amp;gt; all from the item record&lt;/li&gt;
	&lt;li&gt;The feature of yours that is blocked by the call number normalization (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2002&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2002&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement Normalized Call Number for Sorting (LoC Parsing Only)&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-2002
        &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;
) is 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-2128&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2128&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History&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-2128
        &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;
.  I linked those up accordingly.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Finally, when 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1626&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1626&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Store Effective Call Number Prefix, Call Number and Suffix in the Item Record&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-1626
        &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;
 is complete, let&apos;s discuss before you implement 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIU-1171&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIU-1171&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Display call number:  Create shared module to format display call number&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIU-1171
        &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;
.  It may not be necessary to create a shared module for display of call number.    &lt;/p&gt;</comment>
                                                            <comment id="12947" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Mon, 4 Nov 2019 21:25:59 +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;.  Thanks.  I need to take a closer look at this to make sure I understand what is going on.&lt;/p&gt;
</comment>
                                                            <comment id="12949" author="5af5ed55244bc90a106063c7" created="Thu, 21 Nov 2019 10:26:53 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt;.  I&apos;m trying to get a handle on requirements readiness and this one is marked Analysis complete.  I think this should probably be marked Draft again until we have worked out what exactly needs to be done here.  You are close, but we need to make sure your stories are making use of the Effective call number components we are storing as part of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1626&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1626&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Store Effective Call Number Prefix, Call Number and Suffix in the Item Record&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-1626
        &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;
&lt;/p&gt;

&lt;p&gt;I know this isn&apos;t one of your top Fee/fine features, given you are focusing on features that require more testing and training so I don&apos;t think this is urgent.  I just want to get the feature statuses lined up with reality in terms of readiness.  Does that make sense to you?&lt;/p&gt;</comment>
                                                            <comment id="12952" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Wed, 27 Nov 2019 15:33:50 +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;.  I wasn&apos;t aware of the new &quot;effective call number&quot;, but it is a great idea.  I have changed the Status of this Feature back to &quot;Draft&quot; and will make sure that devs don&apos;t start working on the User Stories.&lt;/p&gt;

&lt;p&gt;In your comment on 24/Oct/19, you say &quot;It may not be necessary to create a shared module for display of call number.&quot;  Is this because we may have a &quot;display effective call number&quot; available on the item record?&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                                                            <comment id="12956" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Fri, 21 Feb 2020 16:59:20 +0000"  >&lt;p&gt;&lt;b&gt;Notes for Circ PO discussion...&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;/rest/api/3/attachment/content/10414&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;</comment>
                                                            <comment id="12958" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Wed, 4 Mar 2020 16:29:41 +0000"  >&lt;p&gt;Per CIRC PO meeting on 2/28/2020, Holly needs to change the user stories to format the display call number format to...&lt;/p&gt;

&lt;p&gt;&amp;lt;Effective Call Number Prefix&amp;gt; &amp;lt;Effective Call Number&amp;gt; &amp;lt;Effective Call Number Suffix&amp;gt; &amp;lt;Volume&amp;gt; &amp;lt;Enumeration&amp;gt; &amp;lt;Chronology&amp;gt; &amp;lt;Effective Copy Number&amp;gt;&lt;/p&gt;

&lt;p&gt;(Full notes available at &lt;a href=&quot;https://docs.google.com/document/d/1y4DjshPNS7SevPGVw2ptdg_Cv52qNfONW1jWhyDL_-w/edit?usp=sharing&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1y4DjshPNS7SevPGVw2ptdg_Cv52qNfONW1jWhyDL_-w/edit?usp=sharing&lt;/a&gt;)&lt;/p&gt;</comment>
                                                            <comment id="12961" author="5af5ed55244bc90a106063c7" created="Thu, 27 Aug 2020 11:23:30 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt;, I think this feature needs to be broken down into two parts:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Display &quot;Effective call number string&quot; throughout Fee/fines pages&lt;/li&gt;
	&lt;li&gt;Support sorting by call number in Fees and Fines&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;The latter is blocked by 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-2002&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2002&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement Normalized Call Number for Sorting (LoC Parsing Only)&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-2002
        &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;
.  The stories here also reference both display and sorting.  We need to remove the sorting bit from the display stories.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A89dc6567-baed-429c-bebb-dfcc7e5dcc50&quot; class=&quot;user-hover&quot; rel=&quot;557058:89dc6567-baed-429c-bebb-dfcc7e5dcc50&quot; data-account-id=&quot;557058:89dc6567-baed-429c-bebb-dfcc7e5dcc50&quot; accountid=&quot;557058:89dc6567-baed-429c-bebb-dfcc7e5dcc50&quot; rel=&quot;noreferrer&quot;&gt;Bohdan Suprun&lt;/a&gt;, if this feature was only about displaying &quot;Effective call number string&quot; on:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;New fee/fine form (after barcode has been added)&lt;/li&gt;
	&lt;li&gt;Fee fine details&lt;/li&gt;
	&lt;li&gt;Fee fine history&lt;br/&gt;
Would there still be backend work needed?  I&apos;m looking to identify front-end only features.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                                                            <comment id="12966" author="557058:89dc6567-baed-429c-bebb-dfcc7e5dcc50" created="Thu, 27 Aug 2020 12:02:47 +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;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;&lt;ins&gt;For the part #1.&lt;/ins&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;New fee/fine form (after barcode has been added) - it is UI only.&lt;/li&gt;
	&lt;li&gt;Fee fine details/history - potentially it can be UI only stories, but it means that we&apos;re moving business logic to UI side, what we currently trying to get rid of. So, I&apos;d prefer to have it on BE side. On BE, when we return fee(s)/fine(s) by query, we have to additionally fetch call number components from inventory. (~10 days)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;ins&gt;For the part #2.&lt;/ins&gt; &lt;br/&gt;
Can be solved as duplication the call number components (or just sortable call number) on fee/fine record. What requires cascade changes in circulation, to populate new property where we create automatic fees. It also means that the call number on the fee/fine vs the call number in inventory can be out of sync. If we need keep them sync, then we need to decide how to implement it.&lt;/p&gt;</comment>
                                                            <comment id="12970" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Mon, 14 Sep 2020 18:17:26 +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;:  Sorting of call number is already a separate feature.  It&apos;s 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-2128&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2128&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History&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-2128
        &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;
.  The three stories for this are already written.  See the &apos;is defined by&apos; links.&lt;/p&gt;</comment>
                                                            <comment id="12973" author="5af5ed55244bc90a106063c7" created="Tue, 15 Sep 2020 08:12:43 +0000"  >&lt;blockquote&gt;&lt;p&gt;Cate Boerema: Sorting of call number is already a separate feature. It&apos;s 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-2128&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-2128&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History&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-2128
        &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;
. The three stories for this are already written. See the &apos;is defined by&apos; links.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt;, there are a couple reasons why I thought sorting was in scope for this feature:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;The feature description mentions sorting&lt;/li&gt;
	&lt;li&gt;There are stories linked to this feature as &quot;is defined by&quot; which have scenarios in them around sorting (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UIU-1307&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UIU-1307&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Display call number:  Update Fees/Fines History to display fully-formatted call number&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium&quot; /&gt;
            UIU-1307
        &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;
 scenario 5)&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;As I said, I think the sorting functionality ought to be broken out into that separate feature and removed from the stories here, but it isn&apos;t urgent.  I was originally hoping this feature would be ui-only which would mean we could get it done now (minus the sort bits) but it sounds like there is back end needed just to display the call number.&lt;/p&gt;</comment>
                                                            <comment id="12977" author="62a96ae7192edb006f9f1bf9" created="Mon, 11 Jul 2022 14:23:41 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt;. Can we move this feature to Closed? Or should this feature be moved to Nolana?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="13236">UXPROD-2128</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="11788">UXPROD-2170</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11004">UXPROD-1626</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10008">
                    <name>Defines</name>
                                                                <inwardlinks description="is defined by ">
                                        <issuelink>
            <issuekey id="69285">MODFEE-99</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45346">UIU-1307</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45348">UIU-1308</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45352">UIU-1309</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="45267">UIU-1171</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11291">UXPROD-2002</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="10413" name="CallNumberExamples.jpg" size="263766" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Thu, 22 Mar 2018 19:35:05 +0000"/>
                            <attachment id="10414" name="Display-call-number-notes.JPG" size="95340" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Fri, 21 Feb 2020 16:59:29 +0000"/>
                            <attachment id="10415" name="ItemRecord.png" size="15726" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Mon, 14 Oct 2019 16:09:30 +0000"/>
                            <attachment id="10416" name="Ska&#776;rmavbild 2018-10-02 kl. 13.15.18.png" size="294723" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 2 Oct 2018 11:18:57 +0000"/>
                            <attachment id="10417" name="Ska&#776;rmavbild 2018-10-02 kl. 13.19.33.png" size="208222" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 2 Oct 2018 11:19:56 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10121"><![CDATA[Medium < 5 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10054" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Back End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:a957226f-df85-4fc8-97f4-8b27a26029ed</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="10186"><![CDATA[UNAM]]></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)">Fees/Fines</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:a957226f-df85-4fc8-97f4-8b27a26029ed</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10062" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Kiwi Planning Points (DO NOT CHANGE)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10063" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>PO Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>93.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10045" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Potential Workaround</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Holly:  I believe this is a cross-app issue of importance.  Fees/fines will need to change if Inventory does.</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzyelb:</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="10224"><![CDATA[R2]]></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="10208"><![CDATA[R1]]></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="10240"><![CDATA[R3]]></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="10243"><![CDATA[R1]]></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="10258"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10080" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Leipzig (ERM Aut 2019)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10272"><![CDATA[R5]]></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>Fri, 6 Apr 2018 19:42:14 +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>