<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:13: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-1473] Expose full CQL in the Inventory app search box</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1473</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Copy of description in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-445&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-445&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;expose full CQL in the User app search box&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-445
        &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 the User app):&lt;br/&gt;
Currently we simply allow putting in a plain term that consequently gets quoted and a query for a specified index(es) gets generated.&lt;/p&gt;

&lt;p&gt;(Guys, before we go ahead with that I would like to ensure we have a consensus on this. I think this is the right thing to do since it gives full control to our power users. Lets plan a meeting if you feel we ought to discuss this)&lt;/p&gt;</description>
                <environment></environment>
        <key id="80824">FOLIO-1473</key>
            <summary>Expose full CQL in the Inventory app search box</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>
                                            <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="557058:f80403de-e149-421e-8750-af45c853402f">Charlotte Whitt</reporter>
                                    <labels>
                            <label>for-next-sprint</label>
                            <label>inventory</label>
                            <label>search_enhancements</label>
                    </labels>
                <created>Thu, 6 Sep 2018 12:59:52 +0000</created>
                <updated>Thu, 25 Jun 2020 04:47:12 +0000</updated>
                            <resolved>Tue, 23 Jun 2020 12:53:42 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                <comments>
                                                            <comment id="195598" author="5bffed52a1b46046f530c8f7" created="Thu, 6 Sep 2018 14:37:48 +0000"  >&lt;p&gt;To make this happen, we need to change the way we build queries and submit them to the back-end so that we have the front-end module configure how the CQL-to-PostgreSQL translator interprets queries against no specific index (or, equivalently, against &lt;tt&gt;cql.serverChoice&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;IIRC, the cql2pg translator already has that facility &amp;#8211; is that right, &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;/p&gt;

&lt;p&gt;If so, then we will need to have each of the back-end modules wire out an endpoint that can be used to call that configuration API, so that when we enter (for example) the Inventory module, we&apos;ll call something like&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
PUT /inventory-storage/cql-config/defaultIndexes

title
contributor
isbn
issn
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;and subsequent queries will be expanded accordingly on the server side:&lt;br/&gt;
&lt;tt&gt;water&lt;/tt&gt; -&amp;gt; &lt;tt&gt;(title=&quot;water&quot; or contributor=&quot;water&quot; or isbn=&quot;water&quot; or issn=&quot;water&quot;)&lt;/tt&gt;&lt;br/&gt;
or, more interestingly:&lt;br/&gt;
&lt;tt&gt;smith or jones&lt;/tt&gt; -&amp;gt; &lt;tt&gt;(title=&quot;smith or jones&quot; or contributor=&quot;smith or jones&quot; or isbn=&quot;smith or jones&quot; or issn=&quot;smith or jones&quot;)&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;(This may require enhancement of the Stripes API to give modules a way to send such configuration when we switch to them; more likely, one of the existing React lifecycle methods will give us what we need.)&lt;/p&gt;

&lt;p&gt;Those who have been paying careful attention will notice that in the list of indexes to search by default, I used three (&lt;tt&gt;contributor&lt;/tt&gt;, &lt;tt&gt;isbn&lt;/tt&gt;, &lt;tt&gt;issn&lt;/tt&gt;) that do not yet exist. They will need to be added and supported, in place of the present very nasty hacks whereby a search for &lt;tt&gt;water&lt;/tt&gt; results in this monstrous query being sent:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
(title=&lt;span class=&quot;code-quote&quot;&gt;&quot;water*&quot;&lt;/span&gt; or contributors adj &lt;span class=&quot;code-quote&quot;&gt;&quot;\&quot;&lt;/span&gt;name\&lt;span class=&quot;code-quote&quot;&gt;&quot;: \&quot;&lt;/span&gt;water*\&lt;span class=&quot;code-quote&quot;&gt;&quot;&quot; or identifiers adj &quot;&lt;/span&gt;\&lt;span class=&quot;code-quote&quot;&gt;&quot;value\&quot;&lt;/span&gt;: \&lt;span class=&quot;code-quote&quot;&gt;&quot;water*\&quot;&lt;/span&gt;&quot;)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The present query &quot;works&quot;, but only by knowing the detailed JSON structure of the records in the PostgreSQL database &amp;#8211; the very thing that we have repeatedly told people on the Slack channels not to rely on. So as a sort of Step Zero, we&apos;ll need to get rid of this hack and replace it with support for good, well-behaved CQL queries.&lt;/p&gt;</comment>
                                                            <comment id="195780" author="5ee89462f7aa140abd82d11d" created="Thu, 6 Sep 2018 14:47:08 +0000"  >&lt;p&gt;There is a code example for setting server choice indexes on &lt;a href=&quot;https://github.com/folio-org/cql2pgjson-java#usage&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/cql2pgjson-java#usage&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195782" author="5ee89462f7aa140abd82d11d" created="Thu, 6 Sep 2018 15:06:42 +0000"  >&lt;p&gt;CQL does not have support for arrays. See &lt;a href=&quot;https://folio-org.atlassian.net/browse/CQLPG-24&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/CQLPG-24&lt;/a&gt; &quot;CQL translator: support Array=String&quot;.&lt;/p&gt;</comment>
                                                            <comment id="195783" author="5bffed52a1b46046f530c8f7" created="Thu, 6 Sep 2018 15:15:23 +0000"  >&lt;p&gt;I do not understand the relevance of that observation.&lt;/p&gt;</comment>
                                                            <comment id="195785" author="5ee89462f7aa140abd82d11d" created="Thu, 6 Sep 2018 15:29:22 +0000"  >&lt;p&gt;String fields can easily queried using CQL syntax: &lt;tt&gt;&quot;title=smith or title=jones&quot;&lt;/tt&gt;&lt;br/&gt;
A field like &lt;tt&gt;identifiers&lt;/tt&gt; is an array element. It cannot be queried in an easy way like a string field. The schema does not contain ISBN at all: &lt;a href=&quot;https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/instance-storage.html#instance_storage_instances__instanceId__get&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/instance-storage.html#instance_storage_instances__instanceId__get&lt;/a&gt;&lt;br/&gt;
There is substantial work needed to come up with a solution that works for all those cases.&lt;/p&gt;</comment>
                                                            <comment id="195786" author="5bffed52a1b46046f530c8f7" created="Thu, 6 Sep 2018 16:01:58 +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; Yes, there is work involved! But that isn&apos;t a reason not to do it.&lt;/p&gt;

&lt;p&gt;We need, from the client, to use CQL to express in precise yet abstract terms what we want to find &amp;#8211; e.g. &lt;tt&gt;issn= 0567-7920&lt;/tt&gt;. It&apos;s then up to the back end (whether mod-inventory-storage of cql2pgjson) to translate that into whatever the low-level equivalent is.&lt;/p&gt;

&lt;p&gt;But for application-level client code to know the internal JSON Schema &amp;#8211; that&apos;s really unacceptable. It should never have been committed, let alone survived this long!&lt;/p&gt;</comment>
                                                            <comment id="195788" author="5ee89462f7aa140abd82d11d" created="Thu, 6 Sep 2018 20:15:30 +0000"  >&lt;p&gt;Yes, I fully agree to and support your last post!&lt;/p&gt;</comment>
                                                            <comment id="195789" author="5af5ed55244bc90a106063c7" created="Mon, 22 Jun 2020 15:56:22 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt; can we close this as done?&lt;/p&gt;</comment>
                                                            <comment id="195790" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 23 Jun 2020 12:53:21 +0000"  >&lt;p&gt;Yes, that&apos;s solved when we implemented Query search in Instance, Holdings, and Item segment.&lt;/p&gt;</comment>
                                                            <comment id="195792" author="615afd1cd9820f0070a09ef0" created="Wed, 24 Jun 2020 12:08:06 +0000"  >&lt;p&gt;Short version: I&apos;m not sure this was solved when we implemented query search. Yes, full CQL is exposed, but not in a realistically useful way for array fields.&lt;/p&gt;

&lt;p&gt;Long version: &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; commented that, &quot;A field like &lt;tt&gt;identifiers&lt;/tt&gt; is an array element. It cannot be queried in an easy way like a string field&quot; and &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; added, &quot;We need, from the client, to use CQL to express in precise yet abstract terms what we want to find &#8211; e.g. &lt;tt&gt;issn= 0567-7920&lt;/tt&gt;. It&apos;s then up to the back end (whether mod-inventory-storage of cql2pgjson) to translate that into whatever the low-level equivalent is.&quot;&lt;/p&gt;

&lt;p&gt;We don&apos;t really do that. We handle array searches like ISBN with a special case in the search-options menu. Choosing &quot;Identifier (all)&quot; and entering a value generate a CQL query like &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
query = (identifiers =/@value &lt;span class=&quot;code-quote&quot;&gt;&quot;9786316800312&quot;&lt;/span&gt;) sortby title
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt; 
&lt;p&gt;Choosing &quot;Identifier - ISBN&quot; generates a CQL query like&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
query = (identifiers =/@value/@identifierTypeId=&lt;span class=&quot;code-quote&quot;&gt;&quot;8261054f-be78-422d-bd51-4ed9f33c3422&quot;&lt;/span&gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;9786316800312&quot;&lt;/span&gt;) sortby title
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;That&apos;s a long way from &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
query = (isbn=&lt;span class=&quot;code-quote&quot;&gt;&quot;9786316800312&quot;&lt;/span&gt;)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;There is not an easy way an end user could use &quot;Query search&quot; to search for a specific &quot;System control number&quot;, for example. &lt;/p&gt;

&lt;p&gt;Related, the shape of the instance record includes:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
    &lt;span class=&quot;code-quote&quot;&gt;&quot;identifiers&quot;&lt;/span&gt; : [ {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;identifierTypeId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;5d164f4b-0b15-4e42-ae75-cfcf85318ad9&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;value&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;ocn968777846&quot;&lt;/span&gt;
    }, {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;identifierTypeId&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;8261054f-be78-422d-bd51-4ed9f33c3422&quot;&lt;/span&gt;,
      &lt;span class=&quot;code-quote&quot;&gt;&quot;value&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;9786316800312&quot;&lt;/span&gt;
    },
    ...
    ]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;It seems unfortunate that the identifier-type-name is not included, i.e. to convey that the ID-type &lt;tt&gt;8261054f...&lt;/tt&gt; corresponds to ISBN.&lt;/p&gt;</comment>
                                                            <comment id="195795" author="5bffed52a1b46046f530c8f7" created="Wed, 24 Jun 2020 12:14:43 +0000"  >&lt;p&gt;Absolutely right. (And this comes back to the decision some time ago to make the UUID &quot;8261054f-be78-422d-bd51-4ed9f33c3422&quot;, rather than the name &quot;isbn&quot;, the canonical way to specify the ISBN identifier-type in FOLIO.)&lt;/p&gt;

&lt;p&gt;The key observation here is that, conceptually, CQL supports a set of searchable indexes that are not tied to the physical fields of the database being search in. In practice it&apos;s often useful to provide a one-to-one mapping from database fields to searchable indexes (e.g. search in the index &lt;tt&gt;title&lt;/tt&gt; to do a search in the &lt;tt&gt;title&lt;/tt&gt; field) &#8212; but it is &lt;em&gt;absolutely&lt;/em&gt; the intention of CQL that indexes should be defined that do not have any direct equivalent field in the database. In the present case, cql2pgjson should translate the CQL query &lt;tt&gt;isbn=9786316800312&lt;/tt&gt; into whatever bit of SQL does the appropriate thing with the special UUID.&lt;/p&gt;</comment>
                                                            <comment id="195797" author="5ee89462f7aa140abd82d11d" created="Wed, 24 Jun 2020 18:42:54 +0000"  >&lt;p&gt;
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-413&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-413&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;add &amp;quot;isbn&amp;quot; normalised index&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;
            MODINVSTOR-413
        &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;a href=&quot;https://github.com/folio-org/mod-inventory-storage/commit/46bbea34b4a68ea861c34e1be96fa3e6e68b1db1&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-inventory-storage/commit/46bbea34b4a68ea861c34e1be96fa3e6e68b1db1&lt;/a&gt; ) added the isbn keyword to CQL allowing to enter&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
isbn=9780262012102
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;into the &quot;Query search&quot; box.&lt;br/&gt;
Example: &lt;a href=&quot;https://folio-snapshot-stable.aws.indexdata.com/inventory/view?qindex=querySearch&amp;amp;query=isbn%3D9780262012102&amp;amp;sort=title&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-snapshot-stable.aws.indexdata.com/inventory/view?qindex=querySearch&amp;amp;query=isbn%3D9780262012102&amp;amp;sort=title&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195799" author="5bffed52a1b46046f530c8f7" created="Wed, 24 Jun 2020 19:07:35 +0000"  >&lt;p&gt;That&apos;s brilliant, Julian! You are several dozen steps ahead of me &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;

&lt;p&gt;Just for my curiosity: how much of this work was in cql2pgjson and how much in mod-inventory-storage?&lt;/p&gt;</comment>
                                                            <comment id="195801" author="5ee89462f7aa140abd82d11d" created="Wed, 24 Jun 2020 19:16:21 +0000"  >&lt;p&gt;RMB provides the option to declare an &quot;sqlExpression&quot; in schema.json.&lt;br/&gt;
mod-inventory-storage fills it. In this case it not only extracts the isbn it also applies some isbn normalization. See pull request posted above.&lt;/p&gt;</comment>
                                                            <comment id="195803" author="5bffed52a1b46046f530c8f7" created="Thu, 25 Jun 2020 04:47:12 +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; That is really elegant!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="76841">MODCXMUX-27</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="47134">UIIN-305</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                            <outwardlinks description="clones">
                                        <issuelink>
            <issuekey id="80110">FOLIO-445</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="37563">CQLPG-24</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13094">UXPROD-1015</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|hzyudr:</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>Thu, 6 Sep 2018 14:37:48 +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>