<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 22:32:49 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[MODORDERS-72] Define receiving endpoints in RAML</title>
                <link>https://folio-org.atlassian.net/browse/MODORDERS-72</link>
                <project id="10143" key="MODORDERS">mod-orders</project>
                    <description>&lt;p&gt;Define the RAML for the receiving items/check-in pieces functionality. The details can be found in &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1se-a2owRfHLG5eaAZglx4vLvRClCKGp2wZCfD39ZJRY/view#gid=121556715&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Orders API Listing&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Acceptance Criteria:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Covers all receiving endpoints&lt;/li&gt;
	&lt;li&gt;Passes raml-cop linting&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="59408">MODORDERS-72</key>
            <summary>Define receiving endpoints in RAML</summary>
                <type id="10005" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10309?size=medium">Story</type>
                            <parent id="10790">UXPROD-1146</parent>
                                    <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="10003">Done</resolution>
                                                        <assignee accountid="5cf6c546b87c300f36eb7b9a">Craig McNally</assignee>
                                                                <reporter accountid="5cf6c546b87c300f36eb7b9a">Craig McNally</reporter>
                                    <labels>
                    </labels>
                <created>Wed, 7 Nov 2018 16:10:38 +0000</created>
                <updated>Thu, 24 Jan 2019 19:37:57 +0000</updated>
                            <resolved>Thu, 24 Jan 2019 19:37:57 +0000</resolved>
                                                    <fixVersion>3.0.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="142080" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Wed, 19 Dec 2018 17:27:04 +0000"  >&lt;p&gt;Sample scenarios for &lt;tt&gt;POST&lt;/tt&gt; &lt;tt&gt;/orders/&amp;lt;id&amp;gt;/receive&lt;/tt&gt; or &lt;tt&gt;/orders/&amp;lt;id&amp;gt;/check-in&lt;/tt&gt;. Let&apos;s assume that we are going to receive a few items (check-in a few pieces) for 5 PO lines.&lt;br/&gt;
As far as I can see there are few cases possible:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;All data processed successfully. In this case we might return a 201 (Created) response or 200 (OK) response. According to &lt;a href=&quot;https://tools.ietf.org/html/rfc7231#section-4.3.3&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;POST specification&lt;/a&gt;:
&lt;blockquote&gt;&lt;p&gt;...the origin server SHOULD send a 201 (Created) response containing a Location header field that provides an identifier for the primary resource created...&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;We might to use path to &lt;tt&gt;/receiving_history&lt;/tt&gt; with &lt;tt&gt;query&lt;/tt&gt; param which could be used to return data for the order as a location header.&lt;/p&gt;&lt;/li&gt;
	&lt;li&gt;No any PO lines processed. The 500 response will be sent back.&lt;/li&gt;
	&lt;li&gt;Some of the PO line data entries are processed fully (i.e. inventory and storage&apos;s pieces updated successfully) but a few PO line data entries failed:
	&lt;ul&gt;
		&lt;li&gt;The items in the inventory were not updated so the logic stopped and pieces data is unchanged.&lt;/li&gt;
		&lt;li&gt;Only some of the items in the inventory were updated so the logic updated only corresponding pieces data with receiving status.&lt;/li&gt;
		&lt;li&gt;The items in the inventory were updated successfully but pieces data failed to be updated.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;In the 3rd case we might return 500 response but with json content returning either:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;tt&gt;receiving_collection&lt;/tt&gt;/&lt;tt&gt;checkin_collection&lt;/tt&gt; with only successfully processed entries&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/folio-org/raml/blob/raml1.0/schemas/errors.schema&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;errors&lt;/a&gt; and each &lt;a href=&quot;https://github.com/folio-org/raml/blob/raml1.0/schemas/error.schema&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;error&lt;/a&gt; will describe failed entry.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt; - could you please have a look and advise if you are okay with any of the approaches or you think the behavior should be different.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Piotr&lt;/p&gt;</comment>
                                                            <comment id="142081" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Thu, 20 Dec 2018 13:41:24 +0000"  >&lt;p&gt;This story can be only completed once the changes of the 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODORDERS-90&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODORDERS-90&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update receiveing and checkin schemas&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;
            MODORDERS-90
        &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;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODORDSTOR-31&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODORDSTOR-31&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create receiving_history API and schema&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;
            MODORDSTOR-31
        &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;
 are available in master.&lt;/p&gt;</comment>
                                                            <comment id="142082" author="5cf6c546b87c300f36eb7b9a" created="Thu, 20 Dec 2018 21:02:27 +0000"  >&lt;p&gt;1) I like your idea of using 201 w/ location of receiving_history w/ query, but I can&apos;t think of an elegant way to form the query... All I can think to do is something like:  peiceId== &amp;lt;id1&amp;gt; OR pieceId == &amp;lt;id2&amp;gt;... etc. for each piece being received/checked in.  I think the query could potentially get quite long very quickly, especially given the length of a single uuid.&lt;/p&gt;

&lt;p&gt;We also need to keep in mind that in the receiving case we won&apos;t actually be creating records, but updating existing records.  This may be reason for endpoint semantics to diverge, or we could take a more general approach:&lt;/p&gt;

&lt;p&gt;Return a 200 (no location header) with a json response body containing the locations of the various receiving_history &quot;records&quot;.  We might want to include other information in the response body as well about each piece, so it&apos;s clear which link/location corresponds to which &quot;piece&quot; in the request.   Care must be taken when naming the fields in this schema to avoid confusion... there&apos;s already a &quot;location_id&quot; in the check-in collection schema... maybe use the term &quot;link&quot; instead. &lt;/p&gt;

&lt;p&gt;2, 3) I think we want to be consistent here... I&apos;m on board with returning a response with a list of errors, but we should respond with the regardless of whether they all failed or only one failed.&lt;/p&gt;

&lt;p&gt;It might make sense to combine all this into a single schema where we return some information for each peice in the request, whether it be a link,etc. or an error message.&lt;/p&gt;

&lt;p&gt;Thoughts?&lt;/p&gt;</comment>
                                                            <comment id="142083" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Sat, 22 Dec 2018 06:04:27 +0000"  >&lt;p&gt;Piotr Kalashuk:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Just would like to provide brief summary.&lt;br/&gt;
We agreed that &lt;tt&gt;receiving_collection&lt;/tt&gt; and &lt;tt&gt;checkin_collection&lt;/tt&gt; should be updated to include &lt;tt&gt;piece_id&lt;/tt&gt; so we can return meaningful processing results.&lt;br/&gt;
There are several potential approaches from client perspective to get piece_id&apos;s:&lt;br/&gt;
1. Extend &lt;tt&gt;composite_po_line.json&lt;/tt&gt; schema adding piece info and extend &lt;tt&gt;GET /orders/&amp;lt;id&amp;gt;&lt;/tt&gt; endpoint adding some parameter (like &lt;tt&gt;mode&lt;/tt&gt; with enum values e.g. SUMMARY, FULL_DETAILS, RECEIVING). Depending on this parameter mod-orders will return different content for the &lt;tt&gt;composite_purchase_order&lt;/tt&gt; and &lt;tt&gt;composite_purchase_order&lt;/tt&gt;&lt;br/&gt;
2. Introduce &lt;tt&gt;GET /orders/&amp;lt;id&amp;gt;/receive&lt;/tt&gt; which should return required information to start receiving flow. This should include PO line summary + piece info 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-javascript&quot;&gt;
pieces: {
  piece_items: {
  type: array:
    {
      id,
      status: [Received | Expected]
    }
  },
  received: number
  total: number
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;3. Similar to 2nd but the piece_id&apos;s are not returned when user starts receiving flow but another endpoint introduced to get pieces with Expected] status for PO lines we are going to process&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Craig McNally&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;So the flow would be something like this:&lt;br/&gt;
1) open the orders app, search/filter - a list of orders appears (&lt;tt&gt;GET /orders&lt;/tt&gt;)&lt;br/&gt;
2) select an order - order details appears (&lt;tt&gt;GET /orders/&amp;lt;id&amp;gt;&lt;/tt&gt;)&lt;br/&gt;
3) select the &quot;receive&quot; button in the details pane - the receiving modal comes up and displays receiving info&lt;br/&gt;
&#8226; for each po_line.... (&lt;tt&gt;GET /orders/lines/&amp;lt;id&amp;gt;/pieces&lt;/tt&gt;) - based on mocks we want to see expected &amp;amp; received.&lt;br/&gt;
4) details are entered, e.g. number of each po_line to receive, notes, etc.&lt;br/&gt;
5) form is submitted - &quot;Update Item Details&quot; modal is displayed&lt;br/&gt;
6) item details are entered, e.g. barcode, location, status, etc.&lt;br/&gt;
7) form is submitted ({{POST /orders/&amp;lt;id&amp;gt;/receive)&lt;br/&gt;
8) Receiving History is displayed (&lt;tt&gt;GET /orders/receiving_history -&amp;gt; purchase_order_id == &amp;lt;order id&amp;gt;&lt;/tt&gt;) (edited) &lt;br/&gt;
note that for 8 to work, we need to add &lt;tt&gt;po_line.purchase_order_id&lt;/tt&gt; to the receiving_history view.&lt;br/&gt;
The PO number displayed at the top of this receiving history modal can be parsed from the po_line_number&lt;/p&gt;&lt;/blockquote&gt;</comment>
                                                            <comment id="142084" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Sat, 22 Dec 2018 13:11:31 +0000"  >&lt;p&gt;The raml file update &lt;a href=&quot;https://github.com/folio-org/mod-orders/commit/e58886355a250c369a1de3cc71d8cdea2e99e76f&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;committed to MODORDERS-72-receiving-endpoints&lt;/a&gt; branch.&lt;/p&gt;

&lt;p&gt;There are following dependencies:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;The &lt;a href=&quot;https://github.com/folio-org/acq-models/pull/58&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;PR #58&lt;/a&gt; created to acq-models repository for required schema updates.&lt;/li&gt;
	&lt;li&gt;The changes of the 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODORDSTOR-31&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODORDSTOR-31&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create receiving_history API and schema&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;
            MODORDSTOR-31
        &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;
 should be merged to master of the acq-models repository&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Once both the changes mentioned above are done, the acq-models sub-module in mod-orders should be switched to latest version and pushed to &lt;a href=&quot;https://github.com/folio-org/mod-orders/tree/MODORDERS-72-receiving-endpoints&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;MODORDERS-72-receiving-endpoints&lt;/a&gt;. After this the PR can be created.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Piotr&lt;/p&gt;</comment>
                                                            <comment id="142085" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Mon, 14 Jan 2019 09:34:10 +0000"  >&lt;p&gt;The &lt;a href=&quot;https://github.com/folio-org/acq-models/pull/58&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;PR #58&lt;/a&gt; of the &lt;a href=&quot;https://github.com/folio-org/acq-models/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;acq-models&lt;/a&gt; repository has been merged.&lt;br/&gt;
The &lt;a href=&quot;https://github.com/folio-org/mod-orders/pull/61&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;PR #61&lt;/a&gt; has been opened for &lt;a href=&quot;https://github.com/folio-org/mod-orders&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;mod-orders&lt;/a&gt; repository.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Piotr&lt;/p&gt;</comment>
                                                            <comment id="142086" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Mon, 21 Jan 2019 09:10:33 +0000"  >&lt;p&gt;The &lt;a href=&quot;https://github.com/folio-org/mod-orders/pull/61&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;PR #61&lt;/a&gt; has been merged to master.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://s3.amazonaws.com/foliodocs/api/mod-orders/order.html&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Orders API documentation&lt;/a&gt; now has receiving endpoints.&lt;/p&gt;</comment>
                                                            <comment id="142087" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Wed, 23 Jan 2019 10:23:28 +0000"  >&lt;p&gt;Verification hsa been done against &lt;tt&gt;folio-testing-backend01.aws.indexdata.com&lt;/tt&gt; back-end that all 3 defined endpoints accessible and return expected at this stage 501 (Not Implemented) response:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;45552_thumb&quot; href=&quot;/rest/api/3/attachment/content/45552&quot; title=&quot;API_Test_To_Check_501.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;45552&quot; file-preview-title=&quot;API_Test_To_Check_501.png&quot;&gt;&lt;jira-attachment-thumbnail url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/45552?default=false&quot; jira-url=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/45552&quot; filename=&quot;API_Test_To_Check_501.png&quot;&gt;&lt;img src=&quot;https://folio-org.atlassian.net/rest/api/3/attachment/thumbnail/45552&quot; data-attachment-name=&quot;API_Test_To_Check_501.png&quot; data-attachment-type=&quot;thumbnail&quot; data-media-services-id=&quot;62ea296c-4ac4-45f8-8b20-5a0bb1e6069c&quot; data-media-services-type=&quot;file&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/jira-attachment-thumbnail&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;The following requests used:&lt;br/&gt;
1. Receiving&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;
POST {{protocol}}:&lt;span class=&quot;code-comment&quot;&gt;//{{url}}:{{okapiport}}/orders/receive
&lt;/span&gt;{
  &lt;span class=&quot;code-quote&quot;&gt;&quot;toBeReceived&quot;&lt;/span&gt;: [
    {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;poLineId&quot;&lt;/span&gt;: &lt;span class=&quot;code-quote&quot;&gt;&quot;{{$guid}}&quot;&lt;/span&gt;
    } 
  ],
  &lt;span class=&quot;code-quote&quot;&gt;&quot;totalRecords&quot;&lt;/span&gt;: 1
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;2. Check-in&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;
POST {{protocol}}:&lt;span class=&quot;code-comment&quot;&gt;//{{url}}:{{okapiport}}/orders/check-in
&lt;/span&gt;{
  &lt;span class=&quot;code-quote&quot;&gt;&quot;checkInItems&quot;&lt;/span&gt;: [
    {
      &lt;span class=&quot;code-quote&quot;&gt;&quot;poLineId&quot;&lt;/span&gt;: &lt;span class=&quot;code-quote&quot;&gt;&quot;{{$guid}}&quot;&lt;/span&gt;
    } 
  ],
  &lt;span class=&quot;code-quote&quot;&gt;&quot;totalRecords&quot;&lt;/span&gt;: 1
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;3. Receiving history&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;GET  {{protocol}}:&lt;span class=&quot;code-comment&quot;&gt;//{{url}}:{{okapiport}}/orders/receiving-history&lt;/span&gt;&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="142088" author="5cf6c546b87c300f36eb7b9a" created="Thu, 24 Jan 2019 19:37:57 +0000"  >&lt;p&gt;I too verified this on folio-testing using similar requests and got 501 responses as expected.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="59436">MODORDERS-90</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="59497">MODORDERS-123</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="32470">MODORDSTOR-31</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="59413">MODORDERS-73</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="45552" name="API_Test_To_Check_501.png" size="92928" author="712020:aa2bd653-1e36-4dcb-a90c-03a5108288c4" created="Wed, 23 Jan 2019 10:17:49 +0000"/>
                    </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="10185"><![CDATA[Thunderjet]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxvrz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="688">ACQ Sprint 52</customfieldvalue>
    <customfieldvalue id="693">ACQ Sprint 55</customfieldvalue>
    <customfieldvalue id="686">ACQ Sprint 53</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10044" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10108" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Tester Assignee</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5cf6c546b87c300f36eb7b9a</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 19 Dec 2018 17:27:04 +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>