<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:13:43 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-1490] Enable various tools for validation and editing of RAML files and examples</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1490</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;While doing DMOD-88, some issues arose with the RAML and associated JSON files.&lt;br/&gt;
These were difficult to determine, and additional warning messages from some tools made that harder.&lt;/p&gt;

&lt;p&gt;Also a pre-processing workaround is currently required, to replace the $ref which links parent and child JSON schema files.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80085">FOLIO-1490</key>
            <summary>Enable various tools for validation and editing of RAML files and examples</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="10003">Done</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="61cd0ca0bce5e00069e98be7">David Crossley</reporter>
                                    <labels>
                            <label>lint</label>
                            <label>raml</label>
                    </labels>
                <created>Mon, 12 Dec 2016 04:17:08 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:21 +0000</updated>
                            <resolved>Wed, 12 Sep 2018 13:40:04 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                    <timespent seconds="499500">3 weeks, 2 days, 2 hours, 45 minutes</timespent>
                                <comments>
                                                            <comment id="188444" author="61cd0ca0bce5e00069e98be7" created="Mon, 12 Dec 2016 04:17:33 +0000"  >&lt;p&gt;Add .eslintrc to relevant modules to declare the plugins eslint-plugin-raml and eslint-plugin-json. (Not automating via build for the first phase.)&lt;/p&gt;</comment>
                                                            <comment id="188446" author="61cd0ca0bce5e00069e98be7" created="Mon, 12 Dec 2016 04:17:47 +0000"  >&lt;p&gt;Some of the error and warning messages are obscure. Will list some here with their fix.&lt;/p&gt;</comment>
                                                            <comment id="188447" author="61cd0ca0bce5e00069e98be7" created="Mon, 12 Dec 2016 05:15:19 +0000"  >&lt;p&gt;eslint mod-metadata/doc/api/catalogue.raml&lt;br/&gt;
...&lt;br/&gt;
  18:17  warning  Example does not conform to schema: Content is not valid according to schema: Expected type object but found type array object,array  bad-raml&lt;/p&gt;

&lt;p&gt;Interpretation:&lt;br/&gt;
The &quot;18:17&quot; refers to the line in types/collection.raml &quot;example: &amp;lt;&amp;lt;exampleCollection&amp;gt;&amp;gt;&quot;&lt;br/&gt;
In doc/api/catalogue.raml the &quot;schemaItem&quot; refers to a collection items schema, whereas &quot;schemaCollection&quot; refers to a single item schema. Should be the other way around.&lt;/p&gt;

&lt;p&gt;Fixed in &lt;a href=&quot;https://github.com/folio-org/mod-metadata/commit/6a685b8866ffc0ca31356ed60f956c7a4e093534&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;6a685b8&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="188449" author="63e2a2771b13d42998e4e706" created="Mon, 12 Dec 2016 11:31:46 +0000"  >&lt;p&gt;Well that is embarrassing, I don&apos;t know how those got switched around &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/sad.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;The knowledge base core and catalogue core modules will be deprecated pretty soon. How does es-lint determine which RAML / JSON.Schema files are checked? Is it run on every build?&lt;/p&gt;</comment>
                                                            <comment id="188451" author="61cd0ca0bce5e00069e98be7" created="Tue, 13 Dec 2016 00:14:24 +0000"  >&lt;p&gt;It is not automated to run for every build (as noted above). I should have explained better how to use it manually.&lt;/p&gt;

&lt;p&gt;Install the plugins (&lt;a href=&quot;https://github.com/galk-in/eslint-plugin-raml&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;eslint-plugin-raml&lt;/a&gt; and &lt;a href=&quot;https://github.com/azeemba/eslint-plugin-json&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;eslint-plugin-json&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;The schema and examples and other RAML files are linked from each top-most raml file. So for example do &apos;eslint mod-metadata/doc/api/catalogue.raml&apos; &amp;#8211; the eslint-plugin-raml does find and process all of its pieces.&lt;/p&gt;

&lt;p&gt;The eslint-plugin-raml will also notify when a linked JSON file has issues. Then use the eslint-plugin-json to report the detail, e.g. &apos;eslint schema/instance.json&apos; (a real example is upcoming).&lt;/p&gt;</comment>
                                                            <comment id="188453" author="61cd0ca0bce5e00069e98be7" created="Tue, 13 Dec 2016 05:46:47 +0000"  >&lt;p&gt;Now some examples from mod-users. These occur in other modules too, but mod-users is the smallest so easier to analyse.&lt;/p&gt;</comment>
                                                            <comment id="188454" author="61cd0ca0bce5e00069e98be7" created="Tue, 13 Dec 2016 06:04:32 +0000"  >&lt;p&gt;eslint mod-users/ramls/users.raml&lt;br/&gt;
...&lt;br/&gt;
  35:13  warning  Can not parse JSON: Unexpected token } in JSON at position 426  bad-raml&lt;br/&gt;
  44:17  warning  Can not parse JSON: Unexpected token } in JSON at position 426  bad-raml&lt;br/&gt;
  13:15  warning  Can not parse JSON: Unexpected token } in JSON at position 426  bad-raml&lt;br/&gt;
  56:13  warning  Can not parse JSON: Unexpected token } in JSON at position 426  bad-raml&lt;/p&gt;

&lt;p&gt;Interpretation:&lt;br/&gt;
The single issue is a trailing comma in JSON at examples/user.sample&lt;/p&gt;

&lt;p&gt;The same warning is reported four times. The first two: &quot;35:13 and 44:17&quot; are where &quot;exampleItem&quot; is referenced in raml-util/rtypes/collection.raml file. The second two: &quot;13:15 and 56:13&quot; are where &quot;exampleItem&quot; is referenced in raml-util/rtypes/item-collection.raml file.&lt;/p&gt;

&lt;p&gt;Fixed in &lt;a href=&quot;https://github.com/folio-org/mod-users/commit/8d315b2f56ea89405f85df4333b292821f48cfee&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;8d315b2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To see the detail of the JSON issue: The eslint-plugin-json wants files with *.json extension.&lt;br/&gt;
So &apos;cp examples/user.sample examples/user.json; eslint examples/user.json&apos;&lt;/p&gt;</comment>
                                                            <comment id="188456" author="61cd0ca0bce5e00069e98be7" created="Tue, 13 Dec 2016 06:06:29 +0000"  >&lt;p&gt;eslint mod-users/ramls/users.raml&lt;br/&gt;
...&lt;br/&gt;
  5:11  warning  string is expected  bad-raml&lt;/p&gt;

&lt;p&gt;Interpretation:&lt;br/&gt;
Tracked this to raml-util/traits/searchable.raml which expects the default of string for the &quot;example&quot; but is a JSON object.&lt;/p&gt;

&lt;p&gt;Fix: Not yet applied.&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;5,6c5,6
&amp;lt;           example: |
&amp;lt;             &amp;lt;&amp;lt;example&amp;gt;&amp;gt;
---
&amp;gt;           example: &amp;lt;&amp;lt;example&amp;gt;&amp;gt;
&amp;gt;             type: &quot;object&quot;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="188458" author="61cd0ca0bce5e00069e98be7" created="Tue, 13 Dec 2016 06:20:25 +0000"  >&lt;p&gt;eslint mod-users/ramls/users.raml&lt;br/&gt;
...&lt;br/&gt;
  18:17  warning  Example does not conform to schema: Content is not valid according to schema: Reference could not be resolved: .../mod-users/ramls/schemas/userdata# .../mod-users/ramls/schemas/userdata#  bad-raml&lt;/p&gt;

&lt;p&gt;Interpretation:&lt;br/&gt;
Cannot resolve the reference in schemas/userdataCollection.json to the &quot;userdata&quot; schema.&lt;br/&gt;
Perhaps we could be using JSON Schema &quot;id&quot;, but we are not yet.&lt;/p&gt;

&lt;p&gt;Fix: Not yet applied.&lt;br/&gt;
Refer to the actual filename:&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;10c10
&amp;lt;                 &quot;$ref&quot; : &quot;userdata&quot;
---
&amp;gt;                 &quot;$ref&quot; : &quot;userdata.json&quot;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="188461" author="63e2a2771b13d42998e4e706" created="Mon, 2 Jan 2017 14:48:35 +0000"  >&lt;p&gt;Hi David,&lt;/p&gt;

&lt;p&gt;How is eslint run for the modules?&lt;/p&gt;

&lt;p&gt;Is it intended to be part of the build process during the work on this issue?&lt;/p&gt;</comment>
                                                            <comment id="188463" author="61cd0ca0bce5e00069e98be7" created="Tue, 3 Jan 2017 01:02:17 +0000"  >&lt;p&gt;See above for temporary instructions for how to run eslint manually.&lt;br/&gt;
See Comment &lt;a href=&quot;https://folio-org.atlassian.net/browse/DMOD-117?focusedCommentId=188451&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;A&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;And note the need to apply a temporary workaround for &quot;Reference could not be resolved&quot;.&lt;br/&gt;
See Comment &lt;a href=&quot;https://folio-org.atlassian.net/browse/DMOD-117?focusedCommentId=188458&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;B&lt;/a&gt;.&lt;br/&gt;
Also need to undo that after running eslint. That workaround does not sit well with the raml-module-builder. Might need proper JSON Schema &quot;id&quot;, which i am not familiar with.&lt;/p&gt;

&lt;p&gt;No, not yet intending to add this eslint to the build process. At the moment just using it manually to tidy up all our RAML files.&lt;/p&gt;

&lt;p&gt;I have also been exploring using &quot;raml-tester&quot;, which is used in the &quot;okapi/okapi-core&quot; build process.&lt;/p&gt;</comment>
                                                            <comment id="188464" author="63e2a2771b13d42998e4e706" created="Tue, 3 Jan 2017 13:18:38 +0000"  >&lt;p&gt;Thanks David,&lt;/p&gt;

&lt;p&gt;I thought I&apos;d been through the comments, sorry.&lt;/p&gt;

&lt;p&gt;I thought I&apos;d have a quick go at scripting this, mod-metadata now has a lint.sh script to run eslint (and it replaces the references so the checks pass currently).&lt;/p&gt;</comment>
                                                            <comment id="188466" author="5f8314dfbdef80006f6f572d" created="Tue, 3 Jan 2017 15:22:40 +0000"  >&lt;p&gt;The RAML parser of RMB does not like the latest commit (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1490&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1490&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Enable various tools for validation and editing of RAML files and examples&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-1490
        &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 says:&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;
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:294)
	at java.lang.&lt;span class=&quot;code-object&quot;&gt;Thread&lt;/span&gt;.run(&lt;span class=&quot;code-object&quot;&gt;Thread&lt;/span&gt;.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid RAML definition:
	ERROR mapping values are not allowed here (line 5, col 16)
	at org.raml.jaxrs.codegen.core.AbstractGenerator.run(AbstractGenerator.java:792)
	at org.raml.jaxrs.codegen.core.GeneratorProxy.run(GeneratorProxy.java:40)
	at org.folio.&lt;span class=&quot;code-keyword&quot;&gt;rest&lt;/span&gt;.tools.GenerateRunner.main(GenerateRunner.java)
	... 6 more
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I suggest we revert it. Besides.. The query is supposedly going to be string anyway - because it&apos;s eventually CQL.&lt;/p&gt;</comment>
                                                            <comment id="188468" author="61cd0ca0bce5e00069e98be7" created="Wed, 4 Jan 2017 00:41:53 +0000"  >&lt;p&gt;Reverted in commit &lt;a href=&quot;https://github.com/folio-org/raml/commit/4731f00bb57d3928e596e0ebf2132ecf7b88805b&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;4731f00&lt;/a&gt;. (Oops &#8211; a lesson in testing.)&lt;/p&gt;

&lt;p&gt;So users of eslint-raml, ignore the warning described at &lt;a href=&quot;https://folio-org.atlassian.net/browse/DMOD-117?focusedCommentId=188456&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;comment-12923&lt;/a&gt; above.&lt;/p&gt;</comment>
                                                            <comment id="188469" author="61cd0ca0bce5e00069e98be7" created="Wed, 11 Jan 2017 12:15:11 +0000"  >&lt;p&gt;Added a Python script to &lt;a href=&quot;https://github.com/folio-org/folio-infrastructure/tree/master/run-raml-tools&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-infrastructure/run-raml-tools&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Different tools are used to process a set of RAML files for each module repository.  Each tool has certain capabilities. None seem to report all issues.  So it is useful to run a number of them, and review their output.&lt;/p&gt;

&lt;p&gt;As explained above in this 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1490&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1490&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Enable various tools for validation and editing of RAML files and examples&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-1490
        &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;
, some schema files use &quot;$ref&quot; references to other schema.  This does work for some RAML processing tools, but not for others.  So we temporarily replace its value with the actual filename.&lt;/p&gt;

&lt;p&gt;Currently applying &quot;eslint-raml&quot;, &quot;ramlev&quot;, &quot;ramlfications&quot;.&lt;/p&gt;

&lt;p&gt;The outputs are proving useful for tidying our RAML files, and enhancing the api docs (DMOD-88).&lt;/p&gt;</comment>
                                                            <comment id="188471" author="63e2a2771b13d42998e4e706" created="Thu, 12 Jan 2017 13:12:40 +0000"  >&lt;p&gt;David &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;, would it be useful to use that Python script (using a submodule) in mod-metadata?&lt;/p&gt;</comment>
                                                            <comment id="188472" author="61cd0ca0bce5e00069e98be7" created="Mon, 16 Jan 2017 08:56:04 +0000"  >&lt;p&gt;I had only intended it to be used manually, external to any particular repository, and then review the output. It does install heaps of stuff in NPM local &quot;./node_modules&quot;.&lt;/p&gt;

&lt;p&gt;Also currently it is in a private repo, as i do not yet know where to put such.&lt;/p&gt;
</comment>
                                                            <comment id="188475" author="61cd0ca0bce5e00069e98be7" created="Wed, 8 Feb 2017 06:40:10 +0000"  >&lt;p&gt;Improved the run-raml-tools script: &lt;/p&gt;

&lt;p&gt;Now also apply &quot;raml-tester&quot; via its local proxy.&lt;br/&gt;
Now also generate local api docs using &quot;raml2html&quot; and &quot;raml-fleece&quot;.&lt;/p&gt;</comment>
                                                            <comment id="188479" author="61cd0ca0bce5e00069e98be7" created="Thu, 9 Mar 2017 01:25:26 +0000"  >&lt;p&gt;As explained above, some processing tools handle schema references differently.&lt;br/&gt;
The issue is wider than just eslint-raml and raml2html. This umbrella issue might help to keep in touch:&lt;br/&gt;
&lt;a href=&quot;https://github.com/raml2html/raml2html/issues/327&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;raml2html/issues/327&lt;/a&gt; &quot;Schemas and $ref&quot;.&lt;/p&gt;</comment>
                                                            <comment id="188481" author="61cd0ca0bce5e00069e98be7" created="Thu, 16 Mar 2017 11:45:51 +0000"  >&lt;p&gt;Improved the run-raml-tools script:&lt;/p&gt;

&lt;p&gt;Added &apos;raml-cop&apos; which keeps well up-to-date. It is now my favourite tool.&lt;/p&gt;</comment>
                                                            <comment id="188484" author="61cd0ca0bce5e00069e98be7" created="Wed, 12 Sep 2018 13:40:04 +0000"  >&lt;p&gt;Now we have consistent $ref, and the dereferencer in RMB.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80626">FOLIO-1213</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56714">RMB-56</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80284">FOLIO-573</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_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxifb:</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>Mon, 12 Dec 2016 11:31:46 +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>