Group CVEs #109
Group CVEs #109
Conversation
many times similar CVEs are opened for the same U/S components this patch groups them in the same message and the same assignee to make sure we are not duplicating work triage the issue
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: eshulman2 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| notification.WriteString(slackId) | ||
| notification.WriteString("> ") | ||
|
|
||
| // Format: "CVE-2024-XXXX (Component): ISSUE-1 ISSUE-2 ISSUE-3" |
There was a problem hiding this comment.
For bugs, the message is:<slack_handle> you have been assigned triage of this bug: <link to bug>. Should we try to be more consistent and user friendly with the message that's delivered?
| ) | ||
|
|
||
| // CVEFieldID is the JIRA custom field ID for the CVE identifier | ||
| const CVEFieldID = "customfield_12324749" |
There was a problem hiding this comment.
Where did you get this custom field from? Looking at a CVE issue (https://issues.redhat.com/browse/OCPBUGS-70096), I can't find a customfield_12324749 field.
See https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html for listing the available custom fields.
I suspect we may have to find CVE via the CVE prefix in the title.
many times similar CVEs are opened for the same U/S components this
patch groups them in the same message and the same assignee to make sure
we are not duplicating work triage the issue
Jira: OSASINFRA-4030