<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 05:15:28 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-47866] Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts</title>
                <link>https://jira.mongodb.org/browse/SERVER-47866</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;When a read on a secondary uses kLastApplied/kNoOverlap and encounters a collection catalog conflict, it uses &lt;a href=&quot;https://github.com/mongodb/mongo/blob/682f0540c970ac7f90afd59b1c325b21608fb3bf/src/mongo/db/db_raii.cpp#L193-L238&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;a trick&lt;/a&gt; to reacquire the PBWM lock and read without a timestamp.&lt;/p&gt;

&lt;p&gt;This was necessary because single-phase background index builds would timestamp writes at future timestamps that may never be seen on secondaries (i.e. &quot;ghost timestamps&quot;). This is not necessary now that simultaneous index builds are the only index builds in 4.5+.&lt;/p&gt;</description>
                <environment></environment>
        <key id="1335042">SERVER-47866</key>
            <summary>Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts</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="6" iconUrl="https://jira.mongodb.org/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="success"/>
                                    <resolution id="13201">Fixed</resolution>
                                        <assignee username="louis.williams@mongodb.com">Louis Williams</assignee>
                                    <reporter username="louis.williams@mongodb.com">Louis Williams</reporter>
                        <labels>
                    </labels>
                <created>Thu, 30 Apr 2020 21:11:42 +0000</created>
                <updated>Sun, 29 Oct 2023 22:08:51 +0000</updated>
                            <resolved>Wed, 23 Sep 2020 17:07:20 +0000</resolved>
                                                    <fixVersion>4.8.0</fixVersion>
                                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="4862025" author="xgen-internal-githook" created="Wed, 28 Sep 2022 15:14:05 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Josef Ahmad&apos;, &apos;email&apos;: &apos;josef.ahmad@mongodb.com&apos;, &apos;username&apos;: &apos;josefahmad&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-67538&quot; title=&quot;Multi-doc transactions should fail if on an old, incompatible snapshot&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-67538&quot;&gt;&lt;del&gt;SERVER-67538&lt;/del&gt;&lt;/a&gt; Make multi-doc txns return WCE on index catalog changes&lt;/p&gt;

&lt;p&gt;Background: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47866&quot; title=&quot;Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47866&quot;&gt;&lt;del&gt;SERVER-47866&lt;/del&gt;&lt;/a&gt; stopped bumping the collection&apos;s minimum&lt;br/&gt;
visibility timestamp on catalog changes related to an index; only the&lt;br/&gt;
index&apos;s minimum visibility snapshot continues to be updated. One side&lt;br/&gt;
effect of this change is that a multi-document transaction can read a&lt;br/&gt;
at a snapshot where the index is not yet ready and commit at a&lt;br/&gt;
timestamp when the index is ready, which not intended behaviour and&lt;br/&gt;
can open the opportunity for a race to happen.&lt;/p&gt;

&lt;p&gt;This patch introduces a check for the indices&apos; minimum visible timestamp.&lt;br/&gt;
Attempting to write to an index entry while reading at an incompatible&lt;br/&gt;
timestamp returns a write conflict exception. Locking rules guarantee that&lt;br/&gt;
we see a consistent in-memory view of the indices&apos; minimum visible&lt;br/&gt;
snapshot.&lt;/p&gt;

&lt;p&gt;(cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03)&lt;br/&gt;
(cherry picked from commit 4e80712214658e3c70cecef42680618068448e7f)&lt;br/&gt;
Branch: v5.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/cbc2fa05af5f8ffe0f2c8f3e37bdd9ac34b3ac85&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/cbc2fa05af5f8ffe0f2c8f3e37bdd9ac34b3ac85&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4826862" author="xgen-internal-githook" created="Wed, 14 Sep 2022 17:49:20 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Josef Ahmad&apos;, &apos;email&apos;: &apos;josef.ahmad@mongodb.com&apos;, &apos;username&apos;: &apos;josefahmad&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-67538&quot; title=&quot;Multi-doc transactions should fail if on an old, incompatible snapshot&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-67538&quot;&gt;&lt;del&gt;SERVER-67538&lt;/del&gt;&lt;/a&gt; Make multi-doc txns return WCE on index catalog changes&lt;/p&gt;

&lt;p&gt;Background: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47866&quot; title=&quot;Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47866&quot;&gt;&lt;del&gt;SERVER-47866&lt;/del&gt;&lt;/a&gt; stopped bumping the collection&apos;s minimum&lt;br/&gt;
visibility timestamp on catalog changes related to an index; only the&lt;br/&gt;
index&apos;s minimum visibility snapshot continues to be updated. One side&lt;br/&gt;
effect of this change is that a multi-document transaction can read a&lt;br/&gt;
at a snapshot where the index is not yet ready and commit at a&lt;br/&gt;
timestamp when the index is ready, which not intended behaviour and&lt;br/&gt;
can open the opportunity for a race to happen.&lt;/p&gt;

&lt;p&gt;This patch introduces a check for the indices&apos; minimum visible timestamp.&lt;br/&gt;
Attempting to write to an index entry while reading at an incompatible&lt;br/&gt;
timestamp returns a write conflict exception. Locking rules guarantee that&lt;br/&gt;
we see a consistent in-memory view of the indices&apos; minimum visible&lt;br/&gt;
snapshot.&lt;/p&gt;

&lt;p&gt;(cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03)&lt;br/&gt;
Branch: v6.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/899fb0a1adba6b61094cda293a5ed4fa985c5f64&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/899fb0a1adba6b61094cda293a5ed4fa985c5f64&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4807122" author="xgen-internal-githook" created="Wed, 7 Sep 2022 07:45:27 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Josef Ahmad&apos;, &apos;email&apos;: &apos;josef.ahmad@mongodb.com&apos;, &apos;username&apos;: &apos;josefahmad&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-67538&quot; title=&quot;Multi-doc transactions should fail if on an old, incompatible snapshot&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-67538&quot;&gt;&lt;del&gt;SERVER-67538&lt;/del&gt;&lt;/a&gt; Make multi-doc txns return WCE on index catalog changes&lt;/p&gt;

&lt;p&gt;Background: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47866&quot; title=&quot;Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47866&quot;&gt;&lt;del&gt;SERVER-47866&lt;/del&gt;&lt;/a&gt; stopped bumping the collection&apos;s minimum&lt;br/&gt;
visibility timestamp on catalog changes related to an index; only the&lt;br/&gt;
index&apos;s minimum visibility snapshot continues to be updated. One side&lt;br/&gt;
effect of this change is that a multi-document transaction can read a&lt;br/&gt;
at a snapshot where the index is not yet ready and commit at a&lt;br/&gt;
timestamp when the index is ready, which not intended behaviour and&lt;br/&gt;
can open the opportunity for a race to happen.&lt;/p&gt;

&lt;p&gt;This patch introduces a check for the indices&apos; minimum visible timestamp.&lt;br/&gt;
Attempting to write to an index entry while reading at an incompatible&lt;br/&gt;
timestamp returns a write conflict exception. Locking rules guarantee that&lt;br/&gt;
we see a consistent in-memory view of the indices&apos; minimum visible&lt;br/&gt;
snapshot.&lt;/p&gt;

&lt;p&gt;(cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03)&lt;br/&gt;
Branch: v6.1&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/fd61bf1c3764ee079d3dcde44a2eb24352c22ae5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/fd61bf1c3764ee079d3dcde44a2eb24352c22ae5&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4791003" author="xgen-internal-githook" created="Wed, 31 Aug 2022 08:03:52 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Josef Ahmad&apos;, &apos;email&apos;: &apos;josef.ahmad@mongodb.com&apos;, &apos;username&apos;: &apos;josefahmad&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-67538&quot; title=&quot;Multi-doc transactions should fail if on an old, incompatible snapshot&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-67538&quot;&gt;&lt;del&gt;SERVER-67538&lt;/del&gt;&lt;/a&gt; Make multi-doc txns return WCE on index catalog changes&lt;/p&gt;

&lt;p&gt;Background: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47866&quot; title=&quot;Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47866&quot;&gt;&lt;del&gt;SERVER-47866&lt;/del&gt;&lt;/a&gt; stopped bumping the collection&apos;s minimum&lt;br/&gt;
visibility timestamp on catalog changes related to an index; only the&lt;br/&gt;
index&apos;s minimum visibility snapshot continues to be updated. One side&lt;br/&gt;
effect of this change is that a multi-document transaction can read a&lt;br/&gt;
at a snapshot where the index is not yet ready and commit at a&lt;br/&gt;
timestamp when the index is ready, which not intended behaviour and&lt;br/&gt;
can open the opportunity for a race to happen.&lt;/p&gt;

&lt;p&gt;This patch introduces a check for the indices&apos; minimum visible timestamp.&lt;br/&gt;
Attempting to write to an index entry while reading at an incompatible&lt;br/&gt;
timestamp returns a write conflict exception. Locking rules guarantee that&lt;br/&gt;
we see a consistent in-memory view of the indices&apos; minimum visible&lt;br/&gt;
snapshot.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3407724" author="xgen-internal-githook" created="Wed, 23 Sep 2020 16:49:26 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Louis Williams&apos;, &apos;email&apos;: &apos;louis.williams@mongodb.com&apos;, &apos;username&apos;: &apos;louiswilliams&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47866&quot; title=&quot;Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47866&quot;&gt;&lt;del&gt;SERVER-47866&lt;/del&gt;&lt;/a&gt; Secondary readers do not need to reacquire PBWM lock if there are catalog conflicts&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/669e5650151733738ce8270e5bdf3c5759665316&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/669e5650151733738ce8270e5bdf3c5759665316&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3385902" author="louis.williams" created="Thu, 10 Sep 2020 18:01:28 +0000"  >&lt;p&gt;I ran a &lt;a href=&quot;https://spruce.mongodb.com/version/5f595a683e8e8638835b58b1/tasks&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;patch build experiment here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It seems like this is possible, but one problem I ran into was that &lt;a href=&quot;https://github.com/mongodb/mongo/blob/ce0487190cf69d200028e7f9f4bcd3cefeea805d/src/mongo/db/catalog/catalog_control.cpp#L69&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;rollback preserves the minVisibleSnapshot&lt;/a&gt; from before rollback and reapplies it &lt;a href=&quot;https://github.com/mongodb/mongo/blob/ce0487190cf69d200028e7f9f4bcd3cefeea805d/src/mongo/db/catalog/catalog_control.cpp#L200&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;after rollback&lt;/a&gt;. This is a problem because the minVisible for a collection can be further ahead than any lastApplied timestamp. We should explore whether this is still necessary in its current capacity. &lt;/p&gt;</comment>
                            <comment id="3128768" author="louis.williams" created="Wed, 27 May 2020 18:26:34 +0000"  >&lt;p&gt;The original description omits the main reason why we do this PBWM &quot;trick&quot;. Index builds during initial sync &lt;a href=&quot;https://github.com/mongodb/mongo/blob/9c1c964657fc021f94e3d0e6fb806f6848547045/src/mongo/db/catalog/index_build_block.cpp#L189&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;set the collection minimum visible snapshot to the current cluster time&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;After initial sync, secondaries readers will get catalog conflicts because the collection minimum visible timestamp is a time that it may never see (in a sharded environment).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="641193">SERVER-38341</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="1400036">SERVER-49285</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="2077048">SERVER-67538</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1517205">SERVER-51703</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="1368137">SERVER-48518</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1400036">SERVER-49285</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 23 Sep 2020 16:49:26 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        1 year, 19 weeks 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_17050" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Downstream Team Attention</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16941"><![CDATA[Not Needed]]></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>luke.bonanomi@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            1 year, 19 weeks ago
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_16465" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Linked BF Score</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>23.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>louis.williams@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hxipfj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr53e7:</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_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="4213">Execution Team 2020-09-21</customfieldvalue>
    <customfieldvalue id="4214">Execution Team 2020-10-05</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </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|hxibov:</customfieldvalue>

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