<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 05:13:24 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-47136] Multiversion blacklisting not being respected by burn in tests</title>
                <link>https://jira.mongodb.org/browse/SERVER-47136</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Currently, there is a check whether multiversion testing is configured when filtering out tests based on blacklist in burn_in_test. Multiversion testing is always not configured for this code path, so this filtering never happens.&lt;/p&gt;

&lt;p&gt;As a DAG engineer,&lt;br/&gt;
I&apos;d like to fix this, such that, engineers can blacklist passthrough multiversion tests using the &lt;tt&gt;etc/backports_required_for_multiversion_tests.yml&lt;/tt&gt; and have them excluded from running.&lt;/p&gt;

&lt;p&gt;AC:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Allow filtering of non-passthrough multiversion tests in burn_in_test&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="1292599">SERVER-47136</key>
            <summary>Multiversion blacklisting not being respected by burn in tests</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</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="jason.chan@mongodb.com">Jason Chan</assignee>
                                    <reporter username="alexander.costas@mongodb.com">Alexander Costas</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 Mar 2020 17:14:34 +0000</created>
                <updated>Sun, 29 Oct 2023 22:10:17 +0000</updated>
                            <resolved>Wed, 6 May 2020 19:39:21 +0000</resolved>
                                                    <fixVersion>4.7.0</fixVersion>
                                                        <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="3072560" author="xgen-internal-githook" created="Wed, 6 May 2020 19:36:07 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Jason Chan&apos;, &apos;email&apos;: &apos;jason.chan@10gen.com&apos;, &apos;username&apos;: &apos;jasonjhchan&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47136&quot; title=&quot;Multiversion blacklisting not being respected by burn in tests&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47136&quot;&gt;&lt;del&gt;SERVER-47136&lt;/del&gt;&lt;/a&gt; Fix multiversion blacklisting for replica_sets_multiversion and sharding_multiversion&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/bfaebfa7b5ad725717d1d348ae33bc758028f697&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/bfaebfa7b5ad725717d1d348ae33bc758028f697&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3072218" author="robert.guo" created="Wed, 6 May 2020 17:16:30 +0000"  >&lt;p&gt;We will discuss &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47965&quot; title=&quot;Remove multiverison blacklisting from burn_in_tests.py&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47965&quot;&gt;&lt;del&gt;SERVER-47965&lt;/del&gt;&lt;/a&gt; at our next triage meeting and try to schedule it for shortly after the release. While the workflow for blacklisting tests across versions is certainly clunky, it is not very different to how all other blacklists in resmoke works (for backports that are not pushed concurrently with the commit on master). The reason is that the blacklist goes in the resmoke YAML suite config, not in the separate &lt;tt&gt;backports_required...&lt;/tt&gt; file. So any time the suite definition is updated, people will likely see any existing TODOs and possibly check whether they can be resolved, which is identical to how all other resmoke suites works. &lt;/p&gt;

&lt;p&gt;Again, I&apos;m not trying to redeem the backporting and &quot;forwardporting&quot; experience of blacklists, but the risk of additional lost test coverage seems small to me.&lt;/p&gt;</comment>
                            <comment id="3071690" author="david.bradford" created="Wed, 6 May 2020 14:04:12 +0000"  >&lt;blockquote&gt;&lt;p&gt;My understanding is the same as Tess&apos;s if that&apos;s correct, when can we schedule &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47965&quot; title=&quot;Remove multiverison blacklisting from burn_in_tests.py&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47965&quot;&gt;&lt;del&gt;SERVER-47965&lt;/del&gt;&lt;/a&gt;? I think that having to do another commit on master after backport is an undesirable developer experience that will lead to a lot of tests not getting unblacklisted accidentally.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=robert.guo&quot; class=&quot;user-hover&quot; rel=&quot;robert.guo&quot;&gt;robert.guo&lt;/a&gt; Do you have an idea when &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47965&quot; title=&quot;Remove multiverison blacklisting from burn_in_tests.py&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47965&quot;&gt;&lt;del&gt;SERVER-47965&lt;/del&gt;&lt;/a&gt; might get scheduled?&lt;/p&gt;</comment>
                            <comment id="3071659" author="judah.schvimer" created="Wed, 6 May 2020 13:50:29 +0000"  >&lt;p&gt;My understanding is the same as Tess&apos;s if that&apos;s correct, when can we schedule &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-47965&quot; title=&quot;Remove multiverison blacklisting from burn_in_tests.py&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-47965&quot;&gt;&lt;del&gt;SERVER-47965&lt;/del&gt;&lt;/a&gt;? I think that having to do another commit on master after backport is an undesirable developer experience that will lead to a lot of tests not getting unblacklisted accidentally.&lt;/p&gt;</comment>
                            <comment id="3071489" author="tess.avitabile" created="Wed, 6 May 2020 12:16:28 +0000"  >&lt;p&gt;To check that I understand correctly, does this mean that after backporting, we will need to do another commit on master to remove the test form the &lt;tt&gt;exclude_files&lt;/tt&gt; keys in &lt;tt&gt;replica_sets_multiversion.yml&lt;/tt&gt; and &lt;tt&gt;sharding_multiversion.yml&lt;/tt&gt;?&lt;/p&gt;</comment>
                            <comment id="3069949" author="jason.chan" created="Tue, 5 May 2020 17:56:30 +0000"  >&lt;p&gt;As part of this ticket we decided for a quick fix to stop the bleeding:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;replica_sets_multiversion and sharding_multiversion will no longer be using &lt;tt&gt;etc/backports_required_for_multiversion_tests.yml&lt;/tt&gt; as a blacklisting mechanism to refrain from cluttering &lt;tt&gt;burn_in_tests.py&lt;/tt&gt; with this logic. Instead, we will direct users to add any tests that need to be blacklisted under the &lt;tt&gt;exclude_files&lt;/tt&gt; keys in &lt;tt&gt;replica_sets_multiversion.yml&lt;/tt&gt; and &lt;tt&gt;sharding_multiversion.yml&lt;/tt&gt;. This way, burn_in will rely on existing resmoke logic to detect that these tests should not be run.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="3069110" author="david.bradford" created="Tue, 5 May 2020 13:14:19 +0000"  >&lt;p&gt;The problem with the known quick fix is that it breaks burn_in_tests in a more general way. See &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-46914&quot; title=&quot;burn_in_tests is looking at multiversion in non-multiversion case&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-46914&quot;&gt;&lt;del&gt;SERVER-46914&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="3063657" author="judah.schvimer" created="Thu, 30 Apr 2020 22:15:52 +0000"  >&lt;p&gt;I&apos;ll jump in here to second Jason&apos;s suggestion for a quick temporary fix. I think this is likely causing a lot of confusion for developers in patch builds and I&apos;d be disappointed if we delayed a fix too long.&lt;/p&gt;</comment>
                            <comment id="3063576" author="david.bradford" created="Thu, 30 Apr 2020 21:33:46 +0000"  >&lt;p&gt;I&apos;ve set up a meeting for next week to discuss what we want to do here.&lt;/p&gt;</comment>
                            <comment id="3063505" author="jason.chan" created="Thu, 30 Apr 2020 20:59:15 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.bradford&quot; class=&quot;user-hover&quot; rel=&quot;david.bradford&quot;&gt;david.bradford&lt;/a&gt;That makes sense. I&apos;m hoping we can at least get a quick temporary fix for now to reduce redness in people&apos;s patch builds.&lt;/p&gt;</comment>
                            <comment id="3063476" author="david.bradford" created="Thu, 30 Apr 2020 20:42:49 +0000"  >&lt;p&gt;I&apos;ve been holding off on this because it seems like the wrong approach. burn_in_tests shouldn&apos;t be doing any blacklisting due to multiversion. Tests should likely be blacklisted by resmoke, likely as a selector (see &lt;a href=&quot;https://github.com/mongodb/mongo/blob/ef0e96cef56425a8d9ed23e98d79698260cb70c6/buildscripts/resmokelib/selector.py#L686-L729&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;). That would allow us to not need to blacklist the tests in multiple places.&lt;/p&gt;</comment>
                            <comment id="3063396" author="jason.chan" created="Thu, 30 Apr 2020 20:06:18 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alexander.costas&quot; class=&quot;user-hover&quot; rel=&quot;alexander.costas&quot;&gt;alexander.costas&lt;/a&gt;Do we have an expected timeline for this? We initially had the multiversion test suites disabled for the Upgrade/Downgrade project, but have recently re-enabled them. I expect this to cause some noise on the master branch.&lt;/p&gt;</comment>
                            <comment id="3037004" author="jason.chan" created="Mon, 13 Apr 2020 16:07:31 +0000"  >&lt;p&gt;Currently, the other blacklisting logic is defined here in &lt;a href=&quot;https://github.com/mongodb/mongo/blob/17ada65dd6eef3867c2a2890780002729c0abe41/buildscripts/evergreen_gen_multiversion_tests.py#L395&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;evergreen_gen_multiversion_tests.py&lt;/a&gt;. This script is called in three places:&lt;/p&gt;

&lt;p&gt;1. As part of &lt;a href=&quot;https://github.com/mongodb/mongo/blob/17ada65dd6eef3867c2a2890780002729c0abe41/etc/evergreen.yml#L1679&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;generate randomized multiversion tasks&lt;/a&gt;.&lt;br/&gt;
2. As part of &lt;a href=&quot;https://github.com/mongodb/mongo/blob/17ada65dd6eef3867c2a2890780002729c0abe41/etc/evergreen.yml#L2130&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;generate multiversion tasks&lt;/a&gt;&lt;br/&gt;
3. As part of the &lt;a href=&quot;https://github.com/mongodb/mongo/blob/17ada65dd6eef3867c2a2890780002729c0abe41/etc/evergreen.yml#L7091&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;replica_sets_multiversion&lt;/a&gt; task&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Note: &lt;tt&gt;replica_sets_multiversion&lt;/tt&gt; is a weird one because it&apos;s based on the &lt;tt&gt;replica_sets&lt;/tt&gt; task, which was not yet a generated task at the point of the Mixed version testing project. Therefore, &lt;tt&gt;replica_sets_multiversion&lt;/tt&gt; does not call into the functions in &lt;tt&gt;1&lt;/tt&gt; and &lt;tt&gt;2&lt;/tt&gt; so it required it&apos;s own invocation to the blacklist logic.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;If we move the logic from &lt;tt&gt;evergreen_gen_multiversion_tests.py&lt;/tt&gt; or change the invocation, we should update the places mentioned above.&lt;/p&gt;

&lt;p&gt;However, the logic is a little different between the above and the logic in burn_in_tests so I don&apos;t think we can merge the two completely. Currently, the above logic will update the generated yaml files directly to blacklist the files that should be excluded (by redefining the the &lt;tt&gt;exclude_files&lt;/tt&gt; and &lt;tt&gt;selector&lt;/tt&gt; values in the yaml definition. IIRC, in the burn_in_tests, we used to just skip adding the blacklisted task to the task list.&lt;/p&gt;</comment>
                            <comment id="3036889" author="alexander.costas" created="Mon, 13 Apr 2020 15:24:57 +0000"  >&lt;p&gt;Makes sense to me. &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jason.chan&quot; class=&quot;user-hover&quot; rel=&quot;jason.chan&quot;&gt;jason.chan&lt;/a&gt; This would apply to the other script as well, right? If we make resmoke handle this, we can remove the blacklisting from there.&lt;/p&gt;</comment>
                            <comment id="3036662" author="david.bradford" created="Mon, 13 Apr 2020 13:22:38 +0000"  >&lt;p&gt;After thinking through this, burn_in seems like the wrong place to be doing this blacklisting. The purpose of burn_in is to ensure that tests provide consistent results. By blacklisting tests in burn_in, we are effectively saying &quot;These tests do not provide consistent results&quot;, which doesn&apos;t seem right. &lt;/p&gt;

&lt;p&gt;This blacklisting seems like it is meant to communicate we shouldn&apos;t run this test at all until the specified ticket has been backported to the previous mongo version. If that is the case, then resmoke seems like it would be a better place for this logic, since we wouldn&apos;t want to run the tests regardless of whether they are being run as part of burn_in or as part of a normal run of the suite.&lt;/p&gt;</comment>
                            <comment id="3035519" author="alexander.costas" created="Fri, 10 Apr 2020 20:17:39 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.bradford%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;david.bradford@mongodb.com&quot;&gt;david.bradford@mongodb.com&lt;/a&gt; So here&apos;s the ticket for restoring blacklisting. With two amendments:&lt;/p&gt;

&lt;p&gt;1. These are also passthrough tests.&lt;br/&gt;
2. Multiversion setup is sometimes active for this scripts; we should detect it and do blacklisting when active.&lt;/p&gt;

&lt;p&gt;Right?&lt;/p&gt;</comment>
                            <comment id="3002803" author="jason.chan" created="Thu, 26 Mar 2020 17:34:15 +0000"  >&lt;p&gt;For more context:&lt;/p&gt;

&lt;p&gt;This is for the multiversion passthroughs that were created as part of the Mixed Version Replica Sets Testing project.&lt;/p&gt;

&lt;p&gt;In reference to burn in tests, these passthrough tests can be separated into two categories:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;sharding_multiversion&lt;/tt&gt; and &lt;tt&gt;replica_sets_multiversion&lt;/tt&gt; will be run in the regular &lt;tt&gt;burn_in_tests&lt;/tt&gt; task. Multiversion setup is required to be able to run these tasks in &lt;tt&gt;burn_in_tests&lt;/tt&gt;. For the sake of burn_in_tests, &lt;tt&gt;generate_config.use_multiversion&lt;/tt&gt; will be False even though these are multiversion tests that are meant to be run as part of burn_in.&lt;/p&gt;

&lt;p&gt;All other multiversion passthroughs (eg. &lt;tt&gt;replica_sets_jscore_multiversion_passthrough&lt;/tt&gt;) are run as part of the &lt;tt&gt;burn_in_multiversion_gen&lt;/tt&gt; task. These tasks are generated along this codepath in &lt;a href=&quot;https://github.com/mongodb/mongo/blob/c2f9ac87298c390a4557876a6b2a6f9b836a7efd/buildscripts/burn_in_tests.py#L747&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;burn_in_tests.py&lt;/a&gt;, by indicating that &lt;tt&gt;generate_config.use_multiversion&lt;/tt&gt; is True.&lt;/p&gt;

&lt;p&gt;We separate the tests this way from burn_in due to special logic required to generate the multiversion passthroughs in &lt;tt&gt;burn_in_multiversion_gen&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;The current blacklisting machinery that&apos;s broken in question is the &lt;a href=&quot;https://github.com/mongodb/mongo/blob/c2f9ac87298c390a4557876a6b2a6f9b836a7efd/etc/backports_required_for_multiversion_tests.yml#L1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;etc/backports_required_for_multiversion_tests.yml&lt;/a&gt;. We should remove the &lt;tt&gt;generate_config.use_multiversion&lt;/tt&gt; from the conditional check &lt;a href=&quot;https://github.com/mongodb/mongo/blob/c2f9ac87298c390a4557876a6b2a6f9b836a7efd/buildscripts/burn_in_tests.py#L582&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To test that the blacklisting feature is working again, we should do the following:&lt;br/&gt;
1. Run a patch with some change to a test in &lt;tt&gt;jstests/replsets&lt;/tt&gt; and a test in &lt;tt&gt;jstests/sharding&lt;/tt&gt; that would normally run in &lt;tt&gt;replica_sets_multiversion&lt;/tt&gt; and &lt;tt&gt;sharding_multiversion&lt;/tt&gt; tasks respectively.&lt;br/&gt;
2. Add these tests to the &lt;tt&gt;etc/backports_required_for_multiversion_tests.yml&lt;/tt&gt; file.&lt;br/&gt;
These tests should not be picked up by `burn_in_tests` and `burn_in_tags` tasks.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10420">
                    <name>Backports</name>
                                            <outwardlinks description="backported by">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="1292608">SERVER-47137</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="1344748">SERVER-48048</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1340729">SERVER-47965</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>17.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_12450" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Backport Requested</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="18953"><![CDATA[v4.4]]></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>Thu, 26 Mar 2020 17:34:15 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        3 years, 40 weeks ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<s><a href='https://jira.mongodb.org/browse/SERVER-47137'>SERVER-47137</a></s>]]></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>
                            3 years, 40 weeks ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alexander.costas@mongodb.com</customfieldvalue>
            <customfieldvalue>david.bradford@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>jason.chan@mongodb.com</customfieldvalue>
            <customfieldvalue>judah.schvimer@mongodb.com</customfieldvalue>
            <customfieldvalue>robert.guo@mongodb.com</customfieldvalue>
            <customfieldvalue>tess.avitabile@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hxbldj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr5wnj:</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="3882">Repl 2020-05-18</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|hxb7mv:</customfieldvalue>

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