<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 05:01:26 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 append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-42789] Add query execution statistics to slow query log line to help identify efficiency of data access plan</title>
                <link>https://jira.mongodb.org/browse/SERVER-42789</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Currently, the value of &lt;tt&gt;nreturned&lt;/tt&gt; reports the number of documents returned by an aggregation after all of the transformations have been applied.  That number is not useful for determining the ratio of scanned / returned for the $cursor.  More useful would be knowing, in addition, the number of documents retrieved by $cursor.&lt;/p&gt;</description>
                <environment></environment>
        <key id="892379">SERVER-42789</key>
            <summary>Add query execution statistics to slow query log line to help identify efficiency of data access plan</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="1" iconUrl="https://jira.mongodb.org/images/icons/statuses/open.png" description="">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="backlog-query-execution">Backlog - Query Execution</assignee>
                                    <reporter username="eric.sommer@mongodb.com">Eric Sommer</reporter>
                        <labels>
                    </labels>
                <created>Tue, 13 Aug 2019 12:39:02 +0000</created>
                <updated>Tue, 2 Jan 2024 16:04:44 +0000</updated>
                                                            <fixVersion>5.0 Desired</fixVersion>
                                    <component>Aggregation Framework</component>
                    <component>Diagnostics</component>
                                        <votes>6</votes>
                                    <watches>45</watches>
                                                                                                                <comments>
                            <comment id="5979730" author="charlie.swanson" created="Tue, 2 Jan 2024 16:04:44 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=john.morales%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;john.morales@mongodb.com&quot;&gt;john.morales@mongodb.com&lt;/a&gt; brought up this ticket at a recent 6WR for PM-3268. I wanted to highlight for watchers that:&lt;/p&gt;


&lt;ol&gt;
	&lt;li&gt;We will consider this for INIT-377, to discuss at next initiative review&lt;/li&gt;
	&lt;li&gt;This ticket tracks a very particular ask about $cursor and agg with $match/$group. There are related issues lurking here like how $unwind can similarly change nReturned. It may be better to triage this as an epic (I see PM-2555 is already filed which is great) so that we can have a design review to ensure what we are building will handle the right cases.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;cc &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer@mongodb.com&quot;&gt;judah.schvimer@mongodb.com&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=james.wahlin%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;james.wahlin@mongodb.com&quot;&gt;james.wahlin@mongodb.com&lt;/a&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="3636120" author="david.storch" created="Thu, 25 Feb 2021 22:08:09 +0000"  >&lt;p&gt;A few notes on the POC:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;We need to explore how similar behavior can be implemented with the slot-based execution engine (SBE). The approach needs to work for both engines, but the POC predates SBE and is pretty tightly tied to the classic execution engine.&lt;/li&gt;
	&lt;li&gt;There was a bug (good find &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=julia.oppenheim&quot; class=&quot;user-hover&quot; rel=&quot;julia.oppenheim&quot;&gt;julia.oppenheim&lt;/a&gt;!) with how &lt;tt&gt;nFiltered&lt;/tt&gt; is reported for getMore operations. In particular, in the POC each getMore reports the cumulative &lt;tt&gt;nFiltered&lt;/tt&gt; value. Instead, it should report the &lt;tt&gt;nFiltered&lt;/tt&gt; quantity in a non-cumulative fashion. This needs to be calculated by subtracting the final &lt;tt&gt;nFiltered&lt;/tt&gt; value from the quantity saved at the beginning of the getMore operation.&lt;/li&gt;
&lt;/ol&gt;
</comment>
                            <comment id="3513440" author="alejandro.torrealba" created="Wed, 2 Dec 2020 22:01:08 +0000"  >&lt;p&gt;The next Auto-pilot init sync is scheduled now for Dec 14.&lt;/p&gt;</comment>
                            <comment id="3513403" author="alejandro.torrealba" created="Wed, 2 Dec 2020 21:45:09 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rezwan.khan&quot; class=&quot;user-hover&quot; rel=&quot;rezwan.khan&quot;&gt;rezwan.khan&lt;/a&gt;&#160;- jus synced with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=julia.oppenheim&quot; class=&quot;user-hover&quot; rel=&quot;julia.oppenheim&quot;&gt;julia.oppenheim&lt;/a&gt;. I am scheduling the next Auto-pilot init sync, and we can bring the POC results there, so everybody involved can get it. &lt;/p&gt;

&lt;p&gt;CC: &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=craig.homa&quot; class=&quot;user-hover&quot; rel=&quot;craig.homa&quot;&gt;craig.homa&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ian.whalen&quot; class=&quot;user-hover&quot; rel=&quot;ian.whalen&quot;&gt;ian.whalen&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3502142" author="rezwan.khan" created="Mon, 23 Nov 2020 16:16:30 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=julia.oppenheim&quot; class=&quot;user-hover&quot; rel=&quot;julia.oppenheim&quot;&gt;julia.oppenheim&lt;/a&gt;&#160;is testing this on Wednesday Nov 25th, with aiming to have results to review post Thanksgiving.&#160;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alejandro.torrealba&quot; class=&quot;user-hover&quot; rel=&quot;alejandro.torrealba&quot;&gt;alejandro.torrealba&lt;/a&gt;&#160;- can you setup some time w/ John, me, Julia to review the results?&#160;&lt;/p&gt;</comment>
                            <comment id="3436760" author="alejandro.torrealba" created="Fri, 9 Oct 2020 13:15:46 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ian.whalen&quot; class=&quot;user-hover&quot; rel=&quot;ian.whalen&quot;&gt;ian.whalen&lt;/a&gt;&#160;, comments were made in the &lt;a href=&quot;https://docs.google.com/document/d/13zuSDYul37vunLEIfAvFy3At4xbtZQr-U0MJeFc7XDU/edit&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Init Plan&lt;/a&gt; to indicate the next steps to test the POC.&lt;/p&gt;</comment>
                            <comment id="3409306" author="ian@10gen.com" created="Thu, 24 Sep 2020 13:33:43 +0000"  >&lt;p&gt;since this is tied into the auto-pilot INIT: ping &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rezwan.khan&quot; class=&quot;user-hover&quot; rel=&quot;rezwan.khan&quot;&gt;rezwan.khan&lt;/a&gt; for more info on how that testing went?&lt;/p&gt;</comment>
                            <comment id="3290160" author="jonathan.balsano" created="Fri, 17 Jul 2020 16:09:09 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=craig.homa&quot; class=&quot;user-hover&quot; rel=&quot;craig.homa&quot;&gt;craig.homa&lt;/a&gt;, I believe &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rezwan.khan&quot; class=&quot;user-hover&quot; rel=&quot;rezwan.khan&quot;&gt;rezwan.khan&lt;/a&gt; did some testing on that patch, I&apos;ll let him update here.&lt;/p&gt;</comment>
                            <comment id="2858262" author="justin.seyster" created="Mon, 10 Feb 2020 18:28:46 +0000"  >&lt;p&gt;In addition to naming, there are a few new questions.&lt;/p&gt;

&lt;p&gt;First, should we reconsider how we categorize documents that get filtered out by a FETCH_STAGE? With the current implementation plan, a document will get marked as &lt;em&gt;not&lt;/em&gt; preserved if it is filtered by a FETCH_STAGE. By that standard, the docsScanned:docsPreserved ratio will look the same for a completely covered plan as it does for a plan that has to fetch a lot of documents that ultimately get filtered. I don&apos;t think that&apos;s a huge problem, though, because we still have the nFetched metric to distinguish cases like that.&lt;/p&gt;

&lt;p&gt;Second, will the planned implementation produce reasonable results in the cases of index intersection plans and subquery plans (rooted $or)?&lt;/p&gt;</comment>
                            <comment id="2856919" author="david.storch" created="Mon, 10 Feb 2020 16:20:32 +0000"  >&lt;p&gt;We&apos;ve generated some further questions about how this should behave and require further definition from stakeholders in order for us to make progress.&lt;/p&gt;</comment>
                            <comment id="2755010" author="asya" created="Thu, 23 Jan 2020 15:02:20 +0000"  >&lt;p&gt;&amp;gt; $match that filters documents based on a computed field will not be pushed down&lt;/p&gt;

&lt;p&gt;I agree that the metric as you describe it would be correct - the relevant value is how many documents enter the in memory aggregation pipeline relative to nscanned.&lt;/p&gt;</comment>
                            <comment id="2723299" author="justin.seyster" created="Mon, 13 Jan 2020 22:58:40 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.storch&quot; class=&quot;user-hover&quot; rel=&quot;david.storch&quot;&gt;david.storch&lt;/a&gt; and I met last week to talk over what measurement we should use as the &quot;docsPreserved&quot; value in the log line. We came up with the idea of choosing a particular PlanStage to consider as the output of the &quot;data access method&quot; and counting the number of documents in that stage&apos;s output to determine what &quot;docsPreserved&quot; should be. For each query, the planner establishes the &quot;data access method&quot; portion of the plan with one of the public functions planner_access.h.&lt;/p&gt;

&lt;p&gt;Our plan is to modify the planner so that those functions mark the root QuerySolutionNode of the returned query plan as the data access output. That designation will carry over to the corresponding PlanStage, which will increment the &quot;docsPreserved&quot; measurement for each document it outputs. In aggregation plans, there will never be a $group, $unwind, or similar pipeline stage within the &quot;data access method&quot; subtree of the plan, so we&apos;ll be able to avoid the apples-to-oranges comparison problem that comes with using the ratio of documents scanned / documents returned when a returned document represents multiple input documents (as with $group) or a fraction of an input document (as with $unwind).&lt;/p&gt;

&lt;p&gt;In most cases, this definition of &quot;docsPreserved&quot; will give the exact same results as counting the number of documents out of $cursor, but it will still apply even if future versions of the query planner blur the line between what&apos;s considered part of $cursor and what&apos;s considered part of the remaining pipeline.&lt;/p&gt;

&lt;p&gt;We still have one open question about how to count documents. Is it the correct behavior that our current implementation will count a document as &quot;preserved&quot; even if it gets filtered out by a $match that was not &quot;pushed down&quot; into the data access plan? In particular, a $match that filters documents based on a computed field will not be pushed down. We are of the opinion that this behavior makes sense: we&apos;re primarily interested in how efficient the chosen index was, and we don&apos;t expect that a better index choice will improve a query that&apos;s filtering out documents based on a computed field. I&apos;m interested in any opinions on this, though.&lt;/p&gt;</comment>
                            <comment id="2378158" author="david.storch" created="Mon, 19 Aug 2019 23:20:31 +0000"  >&lt;p&gt;Thanks for filing this request &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=eric.sommer&quot; class=&quot;user-hover&quot; rel=&quot;eric.sommer&quot;&gt;eric.sommer&lt;/a&gt;! The &lt;tt&gt;$cursor&lt;/tt&gt; stage is an implementation detail. I am very reluctant to include information on the log line which is closely coupled with the particulars of the existing execution engine. Furthermore, the query team is planning a substantial refactor in order to unify the execution code used for &lt;tt&gt;aggregate&lt;/tt&gt; with the execution engine used for &lt;tt&gt;find&lt;/tt&gt;. As a consequence of this refactor, we are likely to eliminate the &lt;tt&gt;$cursor&lt;/tt&gt; stage from the execution of most &lt;tt&gt;aggregate&lt;/tt&gt; operations.&lt;/p&gt;

&lt;p&gt;After speaking with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=christopher.harris&quot; class=&quot;user-hover&quot; rel=&quot;christopher.harris&quot;&gt;christopher.harris&lt;/a&gt;, my understanding is that getting a sense of the efficiency or selectivity of the data access plan (i.e. any IXSCAN or FETCH stages) prior to any subsequent $group, $unwind, $lookup, etc. is at the heart of this request. Perhaps we could instead report the percentage or count of documents examined which were preserved by a filter? That way the log line, through the combination of &lt;tt&gt;keysExamined&lt;/tt&gt;, &lt;tt&gt;docsExamined&lt;/tt&gt;, &lt;tt&gt;docsPreserved&lt;/tt&gt;, and &lt;tt&gt;nReturned&lt;/tt&gt; would give you a good snapshot of the query&apos;s performance. For example, query could examine 100 keys, fetch 50 documents, filter out 10 of these resulting in &lt;tt&gt;docsPreserved=40&lt;/tt&gt;, and then return 20 due to a subsequent &lt;tt&gt;$group&lt;/tt&gt;. Would that satisfy this improvement request?&lt;/p&gt;

&lt;p&gt;As a final note, this information should already be available in explain() and will be improved substantially by &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21784&quot; title=&quot;Track &amp;#39;nReturned&amp;#39; and &amp;#39;executionTimeMillis&amp;#39; execution stats for each aggregation pipeline stage and expose via explain&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21784&quot;&gt;&lt;del&gt;SERVER-21784&lt;/del&gt;&lt;/a&gt;, which we are hoping to address in 4.4. However, I imagine that for real-world support and debugging scenarios, having this information readily available in the log line is also important.&lt;/p&gt;</comment>
                            <comment id="2377351" author="craig.homa" created="Mon, 19 Aug 2019 15:53:30 +0000"  >&lt;p&gt;Assigning to &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.storch&quot; class=&quot;user-hover&quot; rel=&quot;david.storch&quot;&gt;david.storch&lt;/a&gt; so he can review and update the description and summary.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10820">
                    <name>Initiative</name>
                                                                <inwardlinks description="included in Initiative">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>11.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="25125"><![CDATA[Query Execution]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5002K00000glf0MQAQ, 5002K00000j2UAXQA2, 5002K00000nmyeMQAQ, 5002K00000pFnjqQAC, 5006R00001ltgklQAA, 5006R00001wNWhKQAW]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 19 Aug 2019 15:53:30 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        5 weeks, 1 day ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-2555</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>charlie.swanson@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            5 weeks, 1 day ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alejandro.torrealba@mongodb.com</customfieldvalue>
            <customfieldvalue>asya.kamsky@mongodb.com</customfieldvalue>
            <customfieldvalue>backlog-query-execution</customfieldvalue>
            <customfieldvalue>charlie.swanson@mongodb.com</customfieldvalue>
            <customfieldvalue>craig.homa@mongodb.com</customfieldvalue>
            <customfieldvalue>david.storch@mongodb.com</customfieldvalue>
            <customfieldvalue>eric.sommer@mongodb.com</customfieldvalue>
            <customfieldvalue>ian@mongodb.com</customfieldvalue>
            <customfieldvalue>jonathan.balsano@mongodb.com</customfieldvalue>
            <customfieldvalue>justin.seyster@mongodb.com</customfieldvalue>
            <customfieldvalue>rezwan.khan@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hvkdcn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr25zz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="3287">Query 2019-12-16</customfieldvalue>
    <customfieldvalue id="3288">Query 2019-12-30</customfieldvalue>
    <customfieldvalue id="3289">Query 2020-01-13</customfieldvalue>
    <customfieldvalue id="3291">Query 2020-02-10</customfieldvalue>
    <customfieldvalue id="3292">Query 2020-02-24</customfieldvalue>
    <customfieldvalue id="4464">Query Execution 2021-03-08</customfieldvalue>
    <customfieldvalue id="4466">Query Execution 2021-03-22</customfieldvalue>
    <customfieldvalue id="4468">Query Execution 2021-04-05</customfieldvalue>
    <customfieldvalue id="4470">Query Execution 2021-04-19</customfieldvalue>
    <customfieldvalue id="4472">Query Execution 2021-05-03</customfieldvalue>
    <customfieldvalue id="4709">Query Execution 2021-07-12</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hvjzlz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>