<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:18:30 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-2138] Version numbers of npm managed backend modules would cause dev versions to be considered later than release</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-2138</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;NPM managed backend modules, like graphql currenlty have dev version numbers like `1.1.1000202`&lt;br/&gt;
Given the number above, `1.1.1000202`, which is a development build towards `1.1.1`, when `1.1.1` is released, the dev version `1.1.1000202` would be considered more up to date as the version number is higher.&lt;/p&gt;</description>
                <environment></environment>
        <key id="81368">FOLIO-2138</key>
            <summary>Version numbers of npm managed backend modules would cause dev versions to be considered later than release</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</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="5bfd62c75f77da6929583d6c">steve.osguthorpe</reporter>
                                    <labels>
                            <label>platform-backlog</label>
                    </labels>
                <created>Tue, 2 Jul 2019 16:00:35 +0000</created>
                <updated>Tue, 2 Feb 2021 11:57:36 +0000</updated>
                            <resolved>Wed, 7 Oct 2020 19:43:23 +0000</resolved>
                                                                    <component>Continuous Integration</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                <comments>
                                                            <comment id="196143" author="5c706fbb47a54a6728e59df2" created="Tue, 2 Jul 2019 16:09:49 +0000"  >&lt;p&gt;Since backend modules don&apos;t get pulled into a yarn platform frontend bundle, I think we do not have the same problem with npm&apos;s dependency resolution for prereleases &amp;#8211; so perhaps for backend NodeJS modules, we can use the same prerelease versioning pattern that we use for Maven builds?&lt;/p&gt;</comment>
                                                            <comment id="196144" author="615afd1cd9820f0070a09ef0" created="Wed, 3 Jul 2019 03:03:45 +0000"  >&lt;p&gt;From &lt;a href=&quot;https://folio-project.slack.com/archives/GFBVAFTAA/p1562083332228800&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Slack&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&lt;tt&gt;~&lt;/tt&gt; and &lt;tt&gt;^&lt;/tt&gt; comparators DO NOT match pre-releases. This means we could be trouble when building a platform and apps ask for two different releases, e.g. &quot;@folio/stripes&quot;: &quot;^2.7.0&quot; and &quot;@folio/stripes&quot;: &quot;^2.8.0-alpha.001&quot;. Apps depend on @folio/stripes only as a peer, to be provided by the platform, so this may just be a problem in workspaces where we&#8217;ll see an &#8220;unmet peer dependency&#8221; warning.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;This is exactly why we did it the way we do it now, IIRC.&lt;/p&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;p&gt;I think the issues are related, but the one doesn&apos;t necessarily resolve the other?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;The issue is that Jenkins relabels dev-builds changing `3.1.0` to `3.1.1000202` rather than `3.1.0000202`.&lt;/p&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;p&gt;If we moved to `-alpha.NNN` instead of artificially inflating the patch number, this would be resolved because `3.1.0-alpha.202` would be correctly recognized as a `pre-3.1.0` release (and to precede both `3.1.0` and `3.1.1`) whereas `3.1.1000202` appears to semver to follow `3.1.1`.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;I believe we discovered an issue with `.0NNNN` patch numbering.&lt;/p&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;&lt;p&gt;Yes, see &lt;a href=&quot;https://semver.org/#spec-item-2&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://semver.org/#spec-item-2&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;right, `.0NNN` is technically invalid, but `.1NNN` is higher than `.1` as noted here.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Perhaps this conversation belongs on the issue...but I think ideally we would &lt;em&gt;like&lt;/em&gt; to use prerelease versions for snapshots, as is conventional. The question is whether the package.json files as configured in platform-core, platform-complete, and stripes will pull them in.&lt;/p&gt;&lt;/blockquote&gt;</comment>
                                                            <comment id="196145" author="5bffed52a1b46046f530c8f7" created="Wed, 3 Jul 2019 08:51:46 +0000"  >&lt;p&gt;Wait wait wait, though. Isn&apos;t it the case that 1.1.1000202 is a development build towards 1.1.2, not 1.1.1?&lt;/p&gt;</comment>
                                                            <comment id="196146" author="5bfd62c75f77da6929583d6c" created="Wed, 3 Jul 2019 09:29:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; Semantically speaking it is not a development version at all. And is the 1000202nd patch of version 1.1. And as 1000202 &amp;gt; 2, it would be selected over 1.1.2 when asking for latest 1.1&lt;/p&gt;

&lt;p&gt;And no, I think if we wanted a dev version towards 1.1.2 (although that would be odd) it would be something like 1.1.2-alpha.1. We should never be developing releases towards patches like 1.1.2 as the last number is meant for fixes/optimizations to existing code. If we are adding any extra functionality that doesn&apos;t break the contracts put in place by the previously released version, then we should be developing towards 1.2 instead like 1.2.0-alpha.1.&lt;/p&gt;</comment>
                                                            <comment id="196147" author="5bffed52a1b46046f530c8f7" created="Wed, 3 Jul 2019 09:47:32 +0000"  >&lt;p&gt;You&apos;re right, I&apos;ve conflated the problem you&apos;re having here with an essentially unrelated practice in depending on not-yet-formally-released features in Stripes modules. Forget I said anything, and sort it out with Wayne and Zak &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                                                            <comment id="196148" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 3 Jul 2019 11:25:21 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=615afd1cd9820f0070a09ef0&quot; class=&quot;user-hover&quot; rel=&quot;615afd1cd9820f0070a09ef0&quot; data-account-id=&quot;615afd1cd9820f0070a09ef0&quot; accountid=&quot;615afd1cd9820f0070a09ef0&quot; rel=&quot;noreferrer&quot;&gt;Zak Burke&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; Are there any problems changing the CI versioning to use preRelease numbering?&lt;/p&gt;</comment>
                                                            <comment id="196149" author="5f9abc1eb45b2e007453f423" created="Wed, 3 Jul 2019 12:04:55 +0000"  >&lt;p&gt;We need to spend more time on this to determine what is impacted before making a versioning change across the board to all NPM-based projects.    The scope of &lt;b&gt;this&lt;/b&gt; issue is just mod-grapql - a backend module. &lt;/p&gt;</comment>
                                                            <comment id="196150" author="5c706fbb47a54a6728e59df2" created="Wed, 3 Jul 2019 12:17:42 +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=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; see related issue 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-2092&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2092&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;use -alpha.NNN pre-release version syntax in npm-folio artifacts&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;
            FOLIO-2092
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
 for discussion of prerelease versioning for frontend modules.&lt;/p&gt;</comment>
                                                            <comment id="196151" author="5bffed52a1b46046f530c8f7" created="Wed, 3 Jul 2019 12:43:55 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; IIRC you are including mod-graphql in at least some of your VM builds. Do you know what you&apos;re doing differently from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bfd62c75f77da6929583d6c&quot; class=&quot;user-hover&quot; rel=&quot;5bfd62c75f77da6929583d6c&quot; data-account-id=&quot;5bfd62c75f77da6929583d6c&quot; accountid=&quot;5bfd62c75f77da6929583d6c&quot; rel=&quot;noreferrer&quot;&gt;steve.osguthorpe&lt;/a&gt; such that this works for you but not for him?&lt;/p&gt;</comment>
                                                            <comment id="196152" author="5bfd62c75f77da6929583d6c" created="Wed, 3 Jul 2019 13:10:42 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; We are deploying modules within K8s which is very different to how the reference builds work ATM. Our build infrastructure assumes that versions that are full releases versions would be present in the release repository, &apos;folio&apos; and not in the dev repository &apos;folioci&apos;. When we can&apos;t find it we ignore it.&lt;/p&gt;

&lt;p&gt;I was initially going to spend some time changing the process for how we consume modules, but I think the issue still stands as important. As presumably the `/install` and `/upgrade` enpoint in okapi would not pick up latest and new versions respectively.&lt;/p&gt;</comment>
                                                            <comment id="196153" author="5c706fbb47a54a6728e59df2" created="Wed, 3 Jul 2019 13:47:10 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bfd62c75f77da6929583d6c&quot; class=&quot;user-hover&quot; rel=&quot;5bfd62c75f77da6929583d6c&quot; data-account-id=&quot;5bfd62c75f77da6929583d6c&quot; accountid=&quot;5bfd62c75f77da6929583d6c&quot; rel=&quot;noreferrer&quot;&gt;steve.osguthorpe&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; &amp;#8211; the reference builds pick up the &quot;latest&quot; version of mod-graphql based on sorting SemVer. Since we are interested in development builds, the high patch number works just fine, even though it is technically kind of wrong, or at least wrongish. When we build reference systems based on releases, we pin to specific versions, which is much less flexible (and less elegant) than what Steve is trying to do, I think. Using prerelease versioning would also allow Okapi to use the &lt;tt&gt;preRelease&lt;/tt&gt; query parameter on the tenant install and upgrade endpoints to filter out prereleases when doing dependency resolution. So I think this is probably a good idea all around for mod-graphql.&lt;/p&gt;</comment>
                                                            <comment id="196154" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 3 Jul 2019 14:06:54 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bfd62c75f77da6929583d6c&quot; class=&quot;user-hover&quot; rel=&quot;5bfd62c75f77da6929583d6c&quot; data-account-id=&quot;5bfd62c75f77da6929583d6c&quot; accountid=&quot;5bfd62c75f77da6929583d6c&quot; rel=&quot;noreferrer&quot;&gt;steve.osguthorpe&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; If this can wait, I would prefer we fix CI snapshot versioning for all NPM packages rather than specifically for mod-graphql. I think we could try to find some time for 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-2092&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2092&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;use -alpha.NNN pre-release version syntax in npm-folio artifacts&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;
            FOLIO-2092
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Blocked&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                                                            <comment id="196155" author="5bffed52a1b46046f530c8f7" created="Wed, 3 Jul 2019 14:22:04 +0000"  >&lt;p&gt;Quite possibly the broader issue can wait. But I do need mod-graphql running in K-Int&apos;s ReShare back-up system. So if there&apos;s a simple workaround that can do that, can we please take the low road and just make it so?&lt;/p&gt;</comment>
                                                            <comment id="196156" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Thu, 4 Jul 2019 10:14:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bfd62c75f77da6929583d6c&quot; class=&quot;user-hover&quot; rel=&quot;5bfd62c75f77da6929583d6c&quot; data-account-id=&quot;5bfd62c75f77da6929583d6c&quot; accountid=&quot;5bfd62c75f77da6929583d6c&quot; rel=&quot;noreferrer&quot;&gt;steve.osguthorpe&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; Guys, thanks for working around this on your end. We&apos;ll try address the CI versioning limitation next sprint, we&apos;re out of bandwidth for this one.&lt;/p&gt;</comment>
                                                            <comment id="196157" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 7 Oct 2020 19:43:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Closing because it&apos;s old, please re-open if still relevant.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="79824">FOLIO-2092</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|hzx3og:zzzy</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </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>Tue, 2 Jul 2019 16:09:49 +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>