<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 06:56:21 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-84924] Ensure that 7.0.0 release does not have any applicable critical or high Coverity issues</title>
                <link>https://jira.mongodb.org/browse/SERVER-84924</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;We should include a screenshot that includes the date of the check, similar to WRITING-14730, for documentation.&lt;/p&gt;</description>
                <environment></environment>
        <key id="2405120">SERVER-84924</key>
            <summary>Ensure that 7.0.0 release does not have any applicable critical or high Coverity issues</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="2" iconUrl="https://jira.mongodb.org/images/icons/priorities/critical.svg">Critical - P2</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="kyle.suarez@mongodb.com">Kyle Suarez</assignee>
                                    <reporter username="judah.schvimer@mongodb.com">Judah Schvimer</reporter>
                        <labels>
                    </labels>
                <created>Mon, 31 Jul 2023 14:47:48 +0000</created>
                <updated>Fri, 12 Jan 2024 02:54:44 +0000</updated>
                            <resolved>Tue, 26 Sep 2023 14:17:36 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="5724158" author="salman.baset" created="Fri, 22 Sep 2023 14:22:05 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt; I have reviewed the revised report and it looks good to me. Thank you so much for completing this. This ticket can be closed.&lt;/p&gt;</comment>
                            <comment id="5722760" author="brooke.miller" created="Thu, 21 Sep 2023 21:43:49 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt; can this be considered resolved and done? &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt; If we don&apos;t hear back from Salman, I think this can be closed. The other doc requested (Third party dependencies validation WRITING-14730) didn&apos;t go through this review process.&lt;/p&gt;</comment>
                            <comment id="5680488" author="kyle.suarez" created="Tue, 5 Sep 2023 17:08:39 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt;, any request for further changes?&lt;/p&gt;</comment>
                            <comment id="5643871" author="brooke.miller" created="Fri, 18 Aug 2023 18:15:01 +0000"  >&lt;p&gt;TY. I assumed that &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt; will copy the entirety of the &quot;Revised Report&quot; sheet. I agree with removing the &quot;Internal Notes&quot; column from that sheet.&lt;/p&gt;</comment>
                            <comment id="5643776" author="kyle.suarez" created="Fri, 18 Aug 2023 17:35:45 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=brooke.miller%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;brooke.miller@mongodb.com&quot;&gt;brooke.miller@mongodb.com&lt;/a&gt;! I made some minor adjustments:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Coverity scans the enterprise modules so I also added &quot;MongoDB Server Enterprise&quot; to the Products line&lt;/li&gt;
	&lt;li&gt;Slight tweak to the description of &quot;No Fix Needed&quot; to include shadowed lambda variables as another example of a &quot;cosmetic issue&quot;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;One question I have for you: is this the exact report we will give to IBM? Or are we going to just copy-paste the final values into a new report? I have a preference for the latter; maybe we need to also remove the internal notes?&lt;/p&gt;</comment>
                            <comment id="5643741" author="brooke.miller" created="Fri, 18 Aug 2023 17:27:21 +0000"  >&lt;p&gt;Thanks, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt;! I modified the &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1b3Dl0xgsFEZl5IxRlgjx71Wu5l75DITjC4MZ46Daz3M/edit#gid=537198265&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;intro of the Revised Report tab&lt;/a&gt; to specify the product this applies to (MongoDB Server Community) and the tool used (Coverity) and updated the format of the legend just to align exactly with the details in the &lt;a href=&quot;http://go/ssdlc-policy.&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://go/ssdlc-policy.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This LGTM.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt; can you please review and comment with an LGTM by next Wednesday so that Kyle can close this out? Thanks!&lt;/p&gt;</comment>
                            <comment id="5637761" author="kyle.suarez" created="Wed, 16 Aug 2023 14:23:26 +0000"  >&lt;p&gt;I went in and analyzed the 30 remaining issues:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;28 of them are no longer issues because the offending code in question is no longer in mainline. (I suspect that these Coverity issues were actually duplicates &amp;#8211; there&apos;s no way currently in Coverity to mark something as a duplicate so they get set to &quot;Pending&quot;.) I&apos;ve marked them all as &quot;No Fix Needed&quot;.&lt;/li&gt;
	&lt;li&gt;One of them (CID 134149) was actually complete. I tracked down the WiredTiger ticket (&lt;a href=&quot;https://jira.mongodb.org/browse/WT-10190&quot; title=&quot;Fix null dereference in __wt_cell_unpack_safe and disable packing with feature flag (CID 134149)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-10190&quot;&gt;&lt;del&gt;WT-10190&lt;/del&gt;&lt;/a&gt;) and realized it was missing the &lt;tt&gt;coverity&lt;/tt&gt; label and did not have the CID in the title; I updated the ticket and added it to the &quot;Jira Tickets Fixed&quot; tab.&lt;/li&gt;
	&lt;li&gt;The last issue (CID 133975) is an Impact=Low redundant test issue that is still open (&lt;a href=&quot;https://jira.mongodb.org/browse/WT-9993&quot; title=&quot;Coverity analysis defect 133975: Redundant test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-9993&quot;&gt;WT-9993&lt;/a&gt;). This ticket was also missing the &lt;tt&gt;coverity&lt;/tt&gt; label which I added in and also linked the ticket in the final report.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Sending this back to review.&lt;/p&gt;</comment>
                            <comment id="5635921" author="kyle.suarez" created="Tue, 15 Aug 2023 19:42:44 +0000"  >&lt;p&gt;Moving this back in progress &#8211; I will investigate the 30 issues with a missing Jira ticket.&lt;/p&gt;</comment>
                            <comment id="5635866" author="brooke.miller" created="Tue, 15 Aug 2023 19:22:13 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt;, after our review meeting today I added a new tab (&quot;Revised Report&quot;). A few updates:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Updated Coverity issues to the applicable status according to our revised status categories (Fix Committed, No Fix Needed, False Positive, and Fix Pending)&lt;/li&gt;
	&lt;li&gt;Included the relevant Jira ticket per Coverity issue&lt;/li&gt;
	&lt;li&gt;Verified that tickets with &quot;Fixed Committed&quot; status indeed had a Jira ticket for the issue which had Fixed, Done or Duplicate Resolutions. If Duplicate, I verified that the linked Duplicate ticket was marked as Fixed, Done.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;However, I was unable to find Jira tickets for 30 Coverity issues previously marked as &quot;Fix Committed&quot;. (29 of these issues are either High or Medium Impact). If no Jira tickets were generated for them, I assume we may need to generate Jira tickets to verify these issues indeed had a fix committed for 7.0.0, or to determine no fix is needed. Do you think that&apos;s feasible, or do you have an alternative suggestion?&lt;/p&gt;</comment>
                            <comment id="5632613" author="kyle.suarez" created="Mon, 14 Aug 2023 15:56:32 +0000"  >&lt;p&gt;Legend is complete and I also did another sweep through the sheet. Moving back to review.&lt;/p&gt;</comment>
                            <comment id="5630006" author="kyle.suarez" created="Fri, 11 Aug 2023 21:34:58 +0000"  >&lt;p&gt;I just noticed the comment by Salman and Brooke that&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We also need to provide explanation of the classification status in this document and how that maps to Action status of &quot;No action&quot;/&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I&apos;ll move this back into Open and I&apos;ll get this done next week before the meeting.&lt;/p&gt;</comment>
                            <comment id="5629731" author="kyle.suarez" created="Fri, 11 Aug 2023 19:38:16 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=brooke.miller%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;brooke.miller@mongodb.com&quot;&gt;brooke.miller@mongodb.com&lt;/a&gt;, I misspoke, it&apos;s actually just 5 issues.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Are those... Unresolved Issues attributed to a High or Medium Impact? (You mentioned Minor but I didn&apos;t follow whether that was related to the Jira Priority or Coverity&apos;s Low Impact.)&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;All 5 issues are &quot;P4 - Minor&quot; in Jira. In Coverity, four of the five issues are Impact = &quot;Low&quot;, so those are fine. The fifth and final issue (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-70518&quot; title=&quot;Coverity analysis defect 122973: Dereference after null check&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-70518&quot;&gt;&lt;del&gt;SERVER-70518&lt;/del&gt;&lt;/a&gt;) is a Medium, but I did some code inspection and actually realized the issue is fixed, so I &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-70518?focusedCommentId=5629687&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-5629687&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;commented&lt;/a&gt; as such in the ticket. (Coverity&apos;s own system actually labeled this issue as &quot;fixed&quot; because it correctly determined the old problematic code no longer exists.)&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;I&apos;d recommend including them for now so that we can have visibility. If they are High / Medium impact, I&apos;d like to understand whether those issues are actively in progress and whether they will be fixed for 7.0.0?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I added all five issues to the very bottom of the sheet. The four low-impact unresolved tickets say &quot;Fix Pending&quot;, and the one medium-impact ticket I said &quot;Done&quot; since the code no longer has the defect.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Can you possibly include the instructions explaining what filters you used to generate this report from Coverity so that we don&apos;t lose insight into this?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I am happy to make a basic guide on how I generated this spreadsheet. (Probably best to track this with another WRITING ticket?) But if we sincerely think that we&apos;ll be moving off Coverity onto a different system, then I&apos;d prefer not to make it super detailed if that work will eventually be obviated.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Also, re: the Jira tickets: how were you able to realize which Coverity Issues mapped to the relevant Jira issue to update the correct Coverity issue ID on the first tab? Just based on the CID being included in the Jira Issue Summary?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Yes, each Jira ticket title has the CID, and then I search for the CID in both the existing exported table as well as looking it up in the Coverity system itself to see what it has to say about that particular defect.&lt;/p&gt;</comment>
                            <comment id="5629602" author="brooke.miller" created="Fri, 11 Aug 2023 18:49:36 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt;! Are those 8 Unresolved Issues attributed to a High or Medium Impact? (You mentioned Minor but I didn&apos;t follow whether that was related to the Jira Priority or Coverity&apos;s Low Impact.) &lt;/p&gt;

&lt;p&gt;I&apos;d recommend including them for now so that we can have visibility. If they are High / Medium impact, I&apos;d like to understand whether those issues are actively in progress and whether they will be fixed for 7.0.0?&lt;/p&gt;

&lt;p&gt;Also, sorry for this manual effort on your behalf. Can you possibly include the instructions explaining what filters you used to generate this report from Coverity so that we don&apos;t lose insight into this? Also, re: the Jira tickets: how were you able to realize which Coverity Issues mapped to the relevant Jira issue to update the correct Coverity issue ID on the first tab? Just based on the CID being included in the Jira Issue Summary?&lt;/p&gt;</comment>
                            <comment id="5629553" author="kyle.suarez" created="Fri, 11 Aug 2023 18:26:52 +0000"  >&lt;p&gt;OK, updates to the sheet:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;I hid the columns &quot;Owner&quot; and &quot;Severity&quot; because the values are always &quot;Unassigned&quot; and &quot;Unspecified&quot; anyway. (We can choose to fully delete them instead of just hiding them if we feel they&apos;re not adding any value.)&lt;/li&gt;
	&lt;li&gt;There is a new column &quot;Classification / Action&quot; which merges together those original two columns so that there&apos;s always a meaningful string.&lt;/li&gt;
	&lt;li&gt;I added a conditional validation rule that would flag any ticket with a final &quot;Classification / Action&quot; of either &quot;Unspecified&quot; or &quot;Undecided&quot;, then went in to add an appropriate action.&lt;/li&gt;
	&lt;li&gt;Regarding the &quot;Pending&quot; ones: it turns out that all of the Coverity tickets listed on the &quot;All Issues&quot; sheet are only including ones that are resolved. That means it doesn&apos;t include the 8 pending tickets that are unresolved. Therefore I went in and replaced all the &quot;Pending&quot; ones such that the action is &quot;Done&quot;.
	&lt;ul&gt;
		&lt;li&gt;Given that the 8 remaining issues are not represented on the sheet, would you like me to add them and say they are still &quot;Fix Pending&quot;?&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="5629376" author="kyle.suarez" created="Fri, 11 Aug 2023 17:19:07 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=brooke.miller%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;brooke.miller@mongodb.com&quot;&gt;brooke.miller@mongodb.com&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;What do you think about consolidating the Classification and Action columns? e.g. False Positive classification and Action of &quot;Undecided&quot; seems confusing? Otherwise, we should update the Action column to make &quot;Undecided&quot; more useful.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Sounds good to me and makes sense. I can write a formula to merge the two columns &amp;#8211; my proposal is to pick &lt;tt&gt;Classification&lt;/tt&gt; first, and fall back to &lt;tt&gt;Action&lt;/tt&gt; if &lt;tt&gt;Classification=Undecided&lt;/tt&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;For Impacts other than Low: if the classification is not &quot;Fix Required&quot;, then the Action should be &quot;No action&quot; instead of &quot;Undecided&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Agreed.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Similarly, we noticed quite a few &quot;Pending&quot; statuses for High / Medium impacted issues. Do those investigations need to be complete still, or is that information outdated?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Sadly that information is outdated. Basically, when I export a Medium/High+ ticket from Coverity to Jira, the classification is generally &quot;Pending&quot;. But when the Jira ticket is resolved, the system does not automatically go back and then update the Coverity status to &quot;Done&quot;. Essentially, anything that wasn&apos;t a false positive or intentional can be considered &quot;Done&quot; &lt;b&gt;except&lt;/b&gt; for the 8 outstanding minor tickets. I can go back and essentially mark them all as fixed but then change the 8 outstanding ones to &quot;Pending&quot; or &quot;Awaiting Fix&quot; or something of the sort.&lt;/p&gt;

&lt;p&gt;I&apos;ll have all these changes made by our meeting and we can discuss / review further.&lt;/p&gt;</comment>
                            <comment id="5629132" author="brooke.miller" created="Fri, 11 Aug 2023 16:06:18 +0000"  >&lt;p&gt;Hey &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt;, I talked with Salman about this and we had a few takeaways. &lt;/p&gt;

&lt;p&gt;We updated the &lt;a href=&quot;http://go/ssdlc-policy&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://go/ssdlc-policy&lt;/a&gt; description to be more specific:&lt;br/&gt;
&lt;b&gt;&lt;em&gt;A report that contains the list of all False positive issues and open Low issues, and validation that there are no unresolved Critical, High or Medium issues. For each False Positive and open Low issue, the report contains the name of the issue, date the issue was reported by the tool, and the severity identified by the tool&lt;/em&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;To align with that:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;What do you think about consolidating the Classification and Action columns? e.g. False Positive classification and Action of &quot;Undecided&quot; seems confusing? Otherwise, we should update the Action column to make &quot;Undecided&quot; more useful. We wouldn&apos;t expect to see any &quot;Undecided&quot; High / Medium impacted issues as the expectation is that all High and Medium impacted issues are resolved.&lt;/li&gt;
	&lt;li&gt;For Impacts other than Low: if the classification is not &quot;Fix Required&quot;, then the Action should be &quot;No action&quot; instead of &quot;Undecided&quot;&lt;/li&gt;
	&lt;li&gt;Similarly, we noticed quite a few &quot;Pending&quot; statuses for High / Medium impacted issues. Do those investigations need to be complete still, or is that information outdated?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I&apos;ll find time next week with you, Salman and Judah (optionally) to get closure on this (thanks for the ping!).&lt;/p&gt;</comment>
                            <comment id="5628746" author="kyle.suarez" created="Fri, 11 Aug 2023 14:19:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=brooke.miller%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;brooke.miller@mongodb.com&quot;&gt;brooke.miller@mongodb.com&lt;/a&gt; and &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;: following up on this after my vacation, is there anything else y&apos;all need for the reports and/or the spreadsheets or is this sufficient for closeout?&lt;/p&gt;</comment>
                            <comment id="5608235" author="kyle.suarez" created="Wed, 2 Aug 2023 17:34:43 +0000"  >&lt;p&gt;Adding a link to the &lt;a href=&quot;https://docs.google.com/spreadsheets/d/1b3Dl0xgsFEZl5IxRlgjx71Wu5l75DITjC4MZ46Daz3M/edit?usp=sharing&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Coverity 7.0 Report&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="5608147" author="kyle.suarez" created="Wed, 2 Aug 2023 17:02:59 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt;, correct, the only issues that are outstanding in Jira are low-priority ones, and all of the high-priority ones have been fixed.&lt;/p&gt;</comment>
                            <comment id="5607930" author="salman.baset" created="Wed, 2 Aug 2023 16:01:05 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kyle.suarez%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;kyle.suarez@mongodb.com&quot;&gt;kyle.suarez@mongodb.com&lt;/a&gt; thank you so much for sharing the screenshots. So if I understand correctly, for 7.0.0, Coverity is only reporting low issues that are not yet fixed, right?&lt;/p&gt;

&lt;p&gt;It would be helpful to generate a Coverity CSV list similar to this one for 6.0&lt;br/&gt;
&lt;a href=&quot;https://docs.google.com/spreadsheets/d/1OgEcsKpAingUJ8GQprVqDg0N2Eu4B2rMmcAdT6jG5C0/edit#gid=1778483548&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.google.com/spreadsheets/d/1OgEcsKpAingUJ8GQprVqDg0N2Eu4B2rMmcAdT6jG5C0/edit#gid=1778483548&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5607793" author="kyle.suarez" created="Wed, 2 Aug 2023 15:21:22 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=salman.baset%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;salman.baset@mongodb.com&quot;&gt;salman.baset@mongodb.com&lt;/a&gt;, tagging you here to please review the screenshots. I figure I will also go ahead and generate the usual CSV we give to IBM and will share that with you when it is ready.&lt;/p&gt;</comment>
                            <comment id="5607730" author="kyle.suarez" created="Wed, 2 Aug 2023 15:08:24 +0000"  >&lt;p&gt;In the Coverity interface itself, here are the outstanding high impact issues. There is only one issue listed, and a fix was committed as part of &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-78538&quot; title=&quot;Coverity analysis defect 123461: Out-of-bounds access&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-78538&quot;&gt;&lt;del&gt;SERVER-78538&lt;/del&gt;&lt;/a&gt; / &lt;a href=&quot;https://jira.mongodb.org/browse/WT-11252&quot; title=&quot;Overrun in __wt_modify_apply_item() when value_format==&amp;#39;S&amp;#39; and value-&amp;gt;size==0&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-11252&quot;&gt;&lt;del&gt;WT-11252&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;466508_thumb&quot; href=&quot;https://jira.mongodb.org/secure/attachment/466508/466508_coverity-high-impact-outstanding.png&quot; title=&quot;coverity-high-impact-outstanding.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;466508&quot; file-preview-title=&quot;coverity-high-impact-outstanding.png&quot;&gt;&lt;img src=&quot;https://jira.mongodb.org/secure/thumbnail/466508/_thumb_466508.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;</comment>
                            <comment id="5607717" author="kyle.suarez" created="Wed, 2 Aug 2023 15:05:34 +0000"  >&lt;p&gt;This screenshot verifies that we have no outstanding issues in Coverity that are severity: Major or higher:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;466505_thumb&quot; href=&quot;https://jira.mongodb.org/secure/attachment/466505/466505_coverity-outstanding-issues-major.png&quot; title=&quot;coverity-outstanding-issues-major.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;466505&quot; file-preview-title=&quot;coverity-outstanding-issues-major.png&quot;&gt;&lt;img src=&quot;https://jira.mongodb.org/secure/thumbnail/466505/_thumb_466505.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;The next screenshot shows all of the remaining unresolved Coverity issues, all of which are Minor or below:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;466504_thumb&quot; href=&quot;https://jira.mongodb.org/secure/attachment/466504/466504_coverity-outstanding-issues-all.png&quot; title=&quot;coverity-outstanding-issues-all.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;466504&quot; file-preview-title=&quot;coverity-outstanding-issues-all.png&quot;&gt;&lt;img src=&quot;https://jira.mongodb.org/secure/thumbnail/466504/_thumb_466504.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;This snapshot was taken on Wednesday, August 2.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="466508" name="coverity-high-impact-outstanding.png" size="696390" author="kyle.suarez@mongodb.com" created="Wed, 2 Aug 2023 15:09:30 +0000"/>
                            <attachment id="466504" name="coverity-outstanding-issues-all.png" size="870602" author="kyle.suarez@mongodb.com" created="Wed, 2 Aug 2023 15:02:12 +0000"/>
                            <attachment id="466505" name="coverity-outstanding-issues-major.png" size="713854" author="kyle.suarez@mongodb.com" created="Wed, 2 Aug 2023 15:02:12 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>23.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 2 Aug 2023 15:05:34 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        19 weeks, 5 days 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>PROG-8288</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>kelly.lewis@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            19 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>brooke.miller@mongodb.com</customfieldvalue>
            <customfieldvalue>judah.schvimer@mongodb.com</customfieldvalue>
            <customfieldvalue>kyle.suarez@mongodb.com</customfieldvalue>
            <customfieldvalue>salman.baset@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i2k6vz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|i22ago:</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="7248">QE 2023-09-04</customfieldvalue>
    <customfieldvalue id="7249">QE 2023-09-18</customfieldvalue>
    <customfieldvalue id="7251">QE 2023-10-02</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|i2jt1b:</customfieldvalue>

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