<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:15:36 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>[FOLIO-1746] SPIKE: When should a major behavioural version be reflected in the implementation version?</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1746</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;&lt;b&gt;Context&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Recently, a &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/227&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull request&lt;/a&gt; was merged for 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-248&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-248&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;filtering /item-storage/items when used with &amp;#39;query=id=XXX&amp;#39; is too slow&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODINVSTOR-248
        &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;
 which contained a known behavioural incompatibility with the existing code.&lt;/p&gt;

&lt;p&gt;This change initially had a change to the major implementation version of the module from &lt;tt&gt;&amp;lt;version&amp;gt;14.1.0-SNAPSHOT&amp;lt;/version&amp;gt;&lt;/tt&gt; to &lt;tt&gt;&amp;lt;version&amp;gt;15.0.0-SNAPSHOT&amp;lt;/version&amp;gt;&lt;/tt&gt; in the pom.xml, however that was removed.&lt;/p&gt;

&lt;p&gt;(A similar issue occurred in the resolution of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1720&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1720&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Testing environment unavailable due to incompatibility between mod-gobi and mod-orders&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1720
        &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;
 where the API itself had changed but the interface versions and implementation versions had not)&lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;https://dev.folio.org/guidelines/release-procedures/#prepare-and-perform-the-source-release&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;release procedures&lt;/a&gt; say:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&quot;For &#8230; the next post-release &#8220;new development version&#8221; &#8230; specify the next &#8220;minor&#8221; version. For example 2.18.0-SNAPSHOT rather than 2.17.1-SNAPSHOT&quot;.&lt;/li&gt;
	&lt;li&gt;&quot;Only the release manager should ever need to write to the NEWS file. Using Jira versions and Git log, they can decide what happened in this branch.&quot;&lt;/li&gt;
	&lt;li&gt;However, the release procedures do not answer the question of this Jira.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;b&gt;Question&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;When a major behavioural change is to be made to a module, when should the version change?&lt;/p&gt;

&lt;p&gt;Should it be within the pull request, prior to it via the next snapshot version of a formal release or afterwards in a separate pull request for a formal release?&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Example&lt;/b&gt;&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Module A has implementation version 14.1.0-SNAPSHOT on the head of master&lt;/li&gt;
	&lt;li&gt;Pull request P has a major breaking implementation change (that means the release version containing this should be 15.0.0)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Should we either:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Release version 14.1.0 formally, setting the next snapshot version to 15.0.0-SNAPSHOT pre-emptively, knowing we want to soon merge the pull request P?&lt;/li&gt;
	&lt;li&gt;Change the version to 15.0.0-SNAPSHOT in the pull request P?&lt;/li&gt;
	&lt;li&gt;Merge pull request P without an implementation version change, and the release manager changes the version during the next formal release to 15.0.0 (without 15.0.0-SNAPSHOT)?&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;If the situation is different and there is a bugfix/patch pull request Q and the last formal release was 14.0.0 when should the version 14.1.0-SNAPSHOT in the pom.xml changed to 14.0.1-SNAPSHOT or 14.0.1?&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Change the version to 14.0.1-SNAPSHOT in a separate pull request before merging Q?&lt;/li&gt;
	&lt;li&gt;Change the version to 14.0.1-SNAPSHOT in the pull request Q?&lt;/li&gt;
	&lt;li&gt;Merge pull request Q without an implementation version change, and the release manager changes the version during the next formal release to 14.0.1 (without 14.0.1-SNAPSHOT)?&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;If I have missed available options, please do feel free to add them. Or ask questions.&lt;/p&gt;</description>
                <environment></environment>
        <key id="81126">FOLIO-1746</key>
            <summary>SPIKE: When should a major behavioural version be reflected in the implementation version?</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <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="10000">Won&apos;t Do</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="63e2a2771b13d42998e4e706">Marc Johnson</reporter>
                                    <labels>
                            <label>platform-backlog</label>
                            <label>potential-decision</label>
                    </labels>
                <created>Mon, 28 Jan 2019 10:43:02 +0000</created>
                <updated>Wed, 25 Jan 2023 14:39:55 +0000</updated>
                            <resolved>Wed, 25 Jan 2023 14:39:55 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                <comments>
                                                            <comment id="194789" author="63e2a2771b13d42998e4e706" created="Mon, 28 Jan 2019 10:47:38 +0000"  >&lt;p&gt;&lt;b&gt;My Personal Perspective&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Option 3, merging without a version change (which occurred for 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-248&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-248&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;filtering /item-storage/items when used with &amp;#39;query=id=XXX&amp;#39; is too slow&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODINVSTOR-248
        &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;
) leads to a snapshot version of the previous version containing the breaking change, which to me is IMO misleading and confusing for potentially client.&lt;/p&gt;

&lt;p&gt;Option 1, involves planning a formal release prior to merging the pull request requiring greater coordination.&lt;/p&gt;

&lt;p&gt;My preference is for option 2, as it does not exclude option 1 if we want to formally release prior to it, whilst also trying to make snapshot versions clear.&lt;/p&gt;</comment>
                                                            <comment id="194792" author="63e2a2771b13d42998e4e706" created="Mon, 28 Jan 2019 10:54:11 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed5e2434bf3a1a91d37a&quot; class=&quot;user-hover&quot; rel=&quot;5bffed5e2434bf3a1a91d37a&quot; data-account-id=&quot;5bffed5e2434bf3a1a91d37a&quot; accountid=&quot;5bffed5e2434bf3a1a91d37a&quot; rel=&quot;noreferrer&quot;&gt;Niels Erik Nielsen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A60cd3f6c-4a6b-4e5b-87ac-bd1f292bf840&quot; class=&quot;user-hover&quot; rel=&quot;557058:60cd3f6c-4a6b-4e5b-87ac-bd1f292bf840&quot; data-account-id=&quot;557058:60cd3f6c-4a6b-4e5b-87ac-bd1f292bf840&quot; accountid=&quot;557058:60cd3f6c-4a6b-4e5b-87ac-bd1f292bf840&quot; rel=&quot;noreferrer&quot;&gt;Adam Chandler&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5d8a51e1bcc5480dd6ddfec7&quot; class=&quot;user-hover&quot; rel=&quot;5d8a51e1bcc5480dd6ddfec7&quot; data-account-id=&quot;5d8a51e1bcc5480dd6ddfec7&quot; accountid=&quot;5d8a51e1bcc5480dd6ddfec7&quot; rel=&quot;noreferrer&quot;&gt;Eric Valuk&lt;/a&gt; I would appreciate your thoughts on this? Feel free to invite other interested people to participate as well.&lt;/p&gt;</comment>
                                                            <comment id="194794" author="5ee89462f7aa140abd82d11d" created="Mon, 28 Jan 2019 11:53:03 +0000"  >&lt;p&gt;I prefer option 3. SNAPSHOT versions can change, they are indented to be used by developers only, and not by any potentially client.&lt;br/&gt;
Create a formal release if there is a client that needs them.&lt;br/&gt;
Jira has the &quot;Fix Version/s&quot; field for each issue where one can see what version change (bugfix/minor/major) this issue requires. Neither NEWS.md nor the -SNAPSHOT version in pom.xml reflect all changed made to master until a formal release is done.&lt;/p&gt;</comment>
                                                            <comment id="194797" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Mon, 28 Jan 2019 12:24:55 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Guys, should we change the interface version in the case of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-248&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-248&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;filtering /item-storage/items when used with &amp;#39;query=id=XXX&amp;#39; is too slow&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            MODINVSTOR-248
        &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;
? In reality we are removing the ability to filter by itemId, so the interface conceptually has changed, even though this is not reflected in the RAML/JSON Schema?&lt;/p&gt;

&lt;p&gt;In general, should we consider changing the interface version for intended major behavioural changes? I am assuming this would then happen on the PR and it can be a hint to the lead maintainer to also bump the major implementation version number.&lt;/p&gt;</comment>
                                                            <comment id="194801" author="63e2a2771b13d42998e4e706" created="Mon, 28 Jan 2019 12:45:20 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; Thanks for updating the description in this issue. Apologies for my initially negative reaction to those edits.&lt;/p&gt;

&lt;p&gt;I&apos;ve attempted to answer the existing questions below. Given that the core platform team owns this decision and my significant bias I shall try to refrain from commenting further unless invited to do so.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Implementation version&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; I&apos;d prefer if we kept the specific mod-inventory-storage decision and the policy guidance conversations separate, although, that may not be as possible as I thought given the different opinions. &lt;/p&gt;

&lt;p&gt;From &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; opinion above, I think he believe we should not change the implementation version until formal release (and presumably base this upon the closed issues in JIRA)?&lt;/p&gt;

&lt;p&gt;I have an obvious and clear bias in both the specific issue for mod-inventory-storage and in the general policy for updating the implementation version during a pull request (much like I also did for news during that conversation). As I believe it is allows people to use the github repository as a source of change information and better reflects expectations for snapshot artefacts.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; have both helped me to realise that is at odds with potential merge conflicts, and the desire to keep pull requests version / change management agnostic, and might make applying changes to bug fix releases more involved.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Interface version&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;@jakub I believe this is a separate policy, though as you suggest, a major interface bump would effectively mean a major implementation version bump is also expected.&lt;/p&gt;

&lt;p&gt;From my recollection of previous conversations, we agreed that interface versions are effectively published by merging to master and therefore should be made within pull requests (and it means that we might move multiple minor versions within a single formal release).&lt;/p&gt;

&lt;p&gt;I think changing the interface version for behaviour not described within the interface itself is a challenging area with significant trade-offs (especially if we intend to support replaceability). I think making that decision depends upon what we include in the interface. &lt;/p&gt;

&lt;p&gt;If the CQL indexes supported are an implicit part of the interface, then yes, this would be a major interface version change too. If we do that, we need to manage that cascade through the various modules that use this interface (which I think we were intending to avoid).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="79913">FOLIO-1718</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="55916">MODINVSTOR-248</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="79913">FOLIO-1718</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <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="10144"><![CDATA[Core: Platform]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="994">CP: ready for planning</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10044" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 28 Jan 2019 11:53:03 +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>