<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:14:11 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-1551] Missing or incomplete documentation of data attributes in many module APIs</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1551</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Many module APIs have missing or incomplete documentation of data attributes.  Documentation for each attribute should include:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;A description of what the attribute means&lt;/li&gt;
	&lt;li&gt;The precise domain of the attribute (range of values, controlled vocabulary, etc.)&lt;/li&gt;
	&lt;li&gt;Whether the attribute is required or optional&lt;/li&gt;
	&lt;li&gt;Where to find referenced data, if the attribute is a foreign key&lt;/li&gt;
	&lt;li&gt;Any other constraints on the data, e.g. whether an attribute allows only unique values&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is needed to ensure data quality for reporting.&lt;/p&gt;

&lt;p&gt;This issue is a blocker for: &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1128&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-1128&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This issue relates to feature issue: &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1414&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-1414&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Two examples of attribute documentation:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;I.

Attribute name:     username
Description:        The user&apos;s login name.  This also serves as an unique,
                    human-readable identifier for the user.
Domain:             String of alphanumeric Unicode characters, beginning with
                    an alphabetic character.  Maximum of 16 characters.
Required:           Yes
References:         N/A
Other constraints:  Unique, but may be reused after the user is deleted.

II.

Attribute name:     patronGroup
Description:        The patron group that the user belongs to.
Domain:             UUID
Required:           Yes
References:         &quot;User Groups&quot; /groups/{groupId} (e.g. mod-users)
Other constraints:  None&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;These examples are intended not to prescribe a documentation format or style but to illustrate further the basic documentation content being requested.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80888">FOLIO-1551</key>
            <summary>Missing or incomplete documentation of data attributes in many module APIs</summary>
                <type id="10006" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium">Umbrella</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="10001">Duplicate</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="70121:8d96963c-ce4c-478d-9023-2de35bc14b67">Nassib Nassar</reporter>
                                    <labels>
                            <label>core</label>
                    </labels>
                <created>Thu, 4 Oct 2018 15:30:16 +0000</created>
                <updated>Tue, 26 Feb 2019 10:45:36 +0000</updated>
                            <resolved>Thu, 7 Feb 2019 15:57:00 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>15</watches>
                                                                <comments>
                                                            <comment id="192626" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 9 Oct 2018 09:28:14 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3A8d96963c-ce4c-478d-9023-2de35bc14b67&quot; class=&quot;user-hover&quot; rel=&quot;70121:8d96963c-ce4c-478d-9023-2de35bc14b67&quot; data-account-id=&quot;70121:8d96963c-ce4c-478d-9023-2de35bc14b67&quot; accountid=&quot;70121:8d96963c-ce4c-478d-9023-2de35bc14b67&quot; rel=&quot;noreferrer&quot;&gt;Nassib Nassar&lt;/a&gt; can you provide examples on how this documentation could be provided? For a selected data elements (e.g controlled vocabulary, UUID) etc. Should this be part of the JSON schema and RAML with a specific syntax used or are we talking about &quot;human-readable&quot; descriptions?&lt;/p&gt;</comment>
                                                            <comment id="192628" author="70121:8d96963c-ce4c-478d-9023-2de35bc14b67" created="Tue, 9 Oct 2018 18:47:34 +0000"  >&lt;p&gt;I have no preference about what form the documentation takes.&lt;/p&gt;</comment>
                                                            <comment id="192630" author="5bffed63a391f63e5a27f6f7" created="Thu, 1 Nov 2018 01:23:27 +0000"  >&lt;p&gt;From my perspective, it seems obvious that the documentation should accompany the interface definitions and get picked up by &lt;a href=&quot;https://dev.folio.org/reference/api/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://dev.folio.org/reference/api/&lt;/a&gt; .... it&apos;s a compelling aspect of FOLIO that the interfaces are all there and available to developers, but we really undermine that aspect by leaving so many interfaces undocumented.. this will impact any client developer and anyone looking to build reporting using any kind of methodology.&lt;/p&gt;

&lt;p&gt;It also seems like there is at least a possibility that documenting these interfaces will ultimately speed up development by reducing wrongful assumptions about how the interfaces are used, and by reducing the need for developers asking other developers about usage.&lt;/p&gt;</comment>
                                                            <comment id="192632" author="70121:8d96963c-ce4c-478d-9023-2de35bc14b67" created="Thu, 1 Nov 2018 03:31:35 +0000"  >&lt;p&gt;I didn&apos;t intend for my response above to be quite so terse.  In my reply to the same question sent by Jakub on Slack, I had added that it&apos;s only the &quot;content&quot; of the documentation that is a problem for reporting, not particularly the &quot;form&quot; it is presented in.  I don&apos;t want to impose more prescriptive detail here than necessary.  For one thing, there may be related considerations in FOLIO that I am unaware of.  The only thing essential for reporting is, I think, that we have the information listed in the Description field above; basically complete documentation of the allowed values for inputs/outputs in the API/interface.  I could offer opinions about what form the information content should take, but I am not really in the best position to make recommendations about that for FOLIO at the moment.  Having said that, I agree with the sentiment above that the documentation should be worked into the JSON schema definition, ideally making use of its self-documenting features if they will be clearly reflected in the autogenerated API documentation, or at least in prose within the description field, which I think is possible for the requested information.&lt;/p&gt;</comment>
                                                            <comment id="192634" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Thu, 1 Nov 2018 10:47:02 +0000"  >&lt;p&gt;Here link to a guideline document which &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5e627525ba96b58654f12&quot; class=&quot;user-hover&quot; rel=&quot;5af5e627525ba96b58654f12&quot; data-account-id=&quot;5af5e627525ba96b58654f12&quot; accountid=&quot;5af5e627525ba96b58654f12&quot; rel=&quot;noreferrer&quot;&gt;Ann-Marie Breaux&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5b44fc07f1230f2c12f1d828&quot; class=&quot;user-hover&quot; rel=&quot;5b44fc07f1230f2c12f1d828&quot; data-account-id=&quot;5b44fc07f1230f2c12f1d828&quot; accountid=&quot;5b44fc07f1230f2c12f1d828&quot; rel=&quot;noreferrer&quot;&gt;Tiziana Possemato&lt;/a&gt; and I started: &lt;a href=&quot;https://docs.google.com/document/d/1T0cQ5SpbuwefPkdpkP9F-olxm6iYcNetg8aRZq7QQ6Y/edit&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://docs.google.com/document/d/1T0cQ5SpbuwefPkdpkP9F-olxm6iYcNetg8aRZq7QQ6Y/edit&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="192636" author="63e2a2771b13d42998e4e706" created="Thu, 1 Nov 2018 16:40:45 +0000"  >&lt;p&gt;I&apos;m probably wading into a conversation that I&apos;m missing some context on, so please let me know if my thoughts are appropriate or valuable, and I can step away if that would be more valuable.&lt;/p&gt;

&lt;p&gt;My interpretation is that the primary purpose of this is to allow developers/users of an interface (or the records, in the case of reporting) to have more understanding of the expectations around what the range of acceptable records are.&lt;/p&gt;

&lt;p&gt;Is that a reasonable summary of the goal?&lt;/p&gt;

&lt;p&gt;In effect this will expand (or at least describe better) the minimal set of behavioural expectations for any implementation as well. How strongly are we expecting implementations to comply to these constraints, e.g. is it a bug if an implementation does not enforce that a value is unique or that a property value is in a specified set?&lt;/p&gt;

&lt;p&gt;As we aren&apos;t able to express much of these constraints (e.g. unique values) in the schema itself, is it intended that much of this will only be in the human readable description property?&lt;/p&gt;

&lt;p&gt;Is this only going to apply to the interfaces/implementations that the core team provides, or is this intended to apply to all FOLIO modules?&lt;/p&gt;

&lt;p&gt;I think we need to be aware of the trade-off between expressing these expectations in the interface and limiting the variability allowed by implementations (e.g. an implementation may not be possible if it wanted to weaken a constraint). And conversely, also expect that implementations may impose further constraints (so not all records fulfilling these expectations may be valid).&lt;/p&gt;

&lt;h6&gt;&lt;a name=&quot;Referencesandcontrolledvocabularies&quot;&gt;&lt;/a&gt;References and controlled vocabularies&lt;/h6&gt;

&lt;blockquote&gt;&lt;p&gt;Where to find referenced data, if the attribute is a foreign key&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Would that take the form of stating which interface would be used to find records referenced by this property?&lt;/p&gt;

&lt;p&gt;I believe this is intended to guide a developer or user about where to find records referenced by this property. &lt;/p&gt;

&lt;p&gt;Is it also intended to set an expectation that an implementation needs to verify that the referred to record exists (during some operations)? In the sense that, clients/users won&apos;t expect to handle that a reference might not be valid (that no record can be found using the reference).&lt;/p&gt;

&lt;p&gt;Is that the same for references to controlled vocabularies (or are the expectations different)?&lt;/p&gt;

&lt;h6&gt;&lt;a name=&quot;Conditionalvalidation&quot;&gt;&lt;/a&gt;Conditional validation&lt;/h6&gt;

&lt;blockquote&gt;&lt;p&gt;Whether the attribute is required or optional&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Does this include conditional situations, where a property is only required when a different property is a particular value? For example, a &lt;tt&gt;userId&lt;/tt&gt; is only required for an open loan, and optional for closed loan, so is optional in the schema (some of our tooling does not allow us to use some of the more complex structures which could describe this explicitly).&lt;/p&gt;</comment>
                                                            <comment id="192641" author="61cd0ca0bce5e00069e98be7" created="Fri, 2 Nov 2018 03:08:35 +0000"  >&lt;p&gt;The document at &lt;a href=&quot;https://dev.folio.org/guides/describe-schema/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;dev.folio.org/guides/describe-schema/&lt;/a&gt; has been improved, and also linked back to these issues for further guidance.&lt;/p&gt;</comment>
                                                            <comment id="192643" author="61cd0ca0bce5e00069e98be7" created="Fri, 2 Nov 2018 03:09:15 +0000"  >&lt;p&gt;Marc, your summary seems spot-on to me. You raise some important technical considerations too.&lt;/p&gt;

&lt;p&gt;Yes this applies to all modules, with emphasis on core modules at this stage. See the related 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-1447&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1447&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;FOLIO policy for RAML and JSON descriptions&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;
            FOLIO-1447
        &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;
 which has links to all back-end RAML-related modules that have missing descriptions.&lt;/p&gt;</comment>
                                                            <comment id="192645" author="63e2a2771b13d42998e4e706" created="Fri, 2 Nov 2018 16:55:20 +0000"  >&lt;p&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; Thanks&lt;/p&gt;</comment>
                                                            <comment id="192648" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 6 Nov 2018 13:56:13 +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; what do you think about the following approach:&lt;/p&gt;

&lt;p&gt;&#8226; for optional attributes: the schema should capture if an attr is optional or mandatory&lt;br/&gt;
&#8226; for allowed values, the schema should include the &#8220;type&#8221; and &#8220;format&#8221; fields to constraint the non-ref values&lt;br/&gt;
&#8226; for referential values &#8212; there&#8217;s no standard in JSON schema to capture this information, so I assume we need something in the description field. By its nature it is not going to be very precise, but still could be helpful. This is probably the hardest one to address because it essentially need some guidelines for people on on how to write &#8220;descriptions&#8221;. David can get something done here.&lt;/p&gt;</comment>
                                                            <comment id="192651" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Nov 2018 07:48:06 +0000"  >&lt;p&gt;Enhanced that &lt;a href=&quot;https://dev.folio.org/guides/describe-schema/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;document&lt;/a&gt; a bit more, following last yesterday&apos;s meeting and the comments here. Also linked to another more complete example.&lt;/p&gt;

&lt;p&gt;(Cache can take 24 hours to propagate, or is available to you now.)&lt;/p&gt;</comment>
                                                            <comment id="192652" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Nov 2018 07:48:51 +0000"  >&lt;p&gt;In RAML 1.0 the &quot;description&quot; nodes can utilise &lt;a href=&quot;https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#markdown&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Markdown&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Should we encourage that to enable links to specific further information?&lt;/p&gt;</comment>
                                                            <comment id="192654" author="5bffed52a1b46046f530c8f7" created="Wed, 9 Jan 2019 17:47:45 +0000"  >&lt;p&gt;The machine-readable link descriptions mentioned in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODGQL-119&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODGQL-119&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate keeping JSON Schema link annotations separate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODGQL-119
        &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;
 may provide what we need.&lt;/p&gt;</comment>
                                                            <comment id="192657" author="70121:8d96963c-ce4c-478d-9023-2de35bc14b67" created="Wed, 9 Jan 2019 17:57:10 +0000"  >&lt;p&gt;Thanks.  My understanding at this time is that 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODGQL-119&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODGQL-119&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate keeping JSON Schema link annotations separate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODGQL-119
        &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;
 documents foreign key relationships but not the other constraints requested in the description of this issue.&lt;/p&gt;</comment>
                                                            <comment id="192659" author="5bffed52a1b46046f530c8f7" created="Thu, 10 Jan 2019 13:28:29 +0000"  >&lt;blockquote&gt;&lt;p&gt;For referential values &#8212; there&#8217;s no standard in JSON schema to capture this information, so I assume we need something in the description field. By its nature it is not going to be very precise, but still could be helpful. This is probably the hardest one to address because it essentially need some guidelines for people on on how to write &#8220;descriptions&#8221;. David can get something done here.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;To note again (possibly new information for the present audience): mod-graphql needs this information in a machine-readable form. I therefore defined some JSON-Schema extension fields, having established that there is no suitable pre-existing standard: see &lt;a href=&quot;https://github.com/folio-org/mod-graphql/blob/master/src/autogen/README.md#option-1-json-schema-extensions&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-graphql/blob/master/src/autogen/README.md#option-1-json-schema-extensions&lt;/a&gt;&lt;br/&gt;
We have added some link-fields that are defined using these extensions: for example, &lt;tt&gt;holdingsRecords2&lt;/tt&gt; in the Instance schema is defined by a specification of how to go out and get holdings records from elsewhere and embed them in the instance: see &lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/blob/1c2571d695bdc500e71a3dfb556df5a7e4564f5d/ramls/instance.json#L303-L316&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-inventory-storage/blob/1c2571d695bdc500e71a3dfb556df5a7e4564f5d/ramls/instance.json#L303-L316&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Note 1&lt;/b&gt;. In general it does &lt;em&gt;not&lt;/em&gt; suffice to say &quot;We&apos;ll add a description to the link field&quot; because sometimes there &lt;em&gt;is&lt;/em&gt; no link field. An instance records doesn&apos;t have a &lt;tt&gt;holdingsId&lt;/tt&gt; field that links to its holdings records; instead, each holdings record has an &lt;tt&gt;instanceId&lt;/tt&gt; that links to its instance record.)&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Note 2&lt;/b&gt;. Does this information properly belong in the JSON Schema? Opinions differ (I say yes), but see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODGQL-119&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODGQL-119&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Investigate keeping JSON Schema link annotations separate&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODGQL-119
        &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;
 for a way to keep our options open on this.&lt;/p&gt;</comment>
                                                            <comment id="192663" author="5af5ed55244bc90a106063c7" created="Thu, 7 Feb 2019 15:57:00 +0000"  >&lt;p&gt;Closing as duplicate of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-1414&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1414&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Complete the documentation of data attributes in module APIs&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-1414
        &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;
.  I&apos;ve moved the requirements from this umbrella into the individual stories as acceptance criteria.  The links have also been migrated.  &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="29739">CIRCSTORE-144</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="67633">MODUSERS-119</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="79910">FOLIO-1447</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="35117">MODGQL-119</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="55901">MODINVSTOR-203</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="10171"><![CDATA[Prokopovych]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 9 Oct 2018 09:28: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>