Pipeline Sec Report: handle Jira issues
requested to merge 443630-create-jira-issue-from-the-security-pipeline-tab-should-not-render-if-there-are-existing into master
What does this MR do and why?
Currently, the pipeline security report does not include any logic to handle existing Jira issues. It does not show any links, or prevents the user from creating duplicates.
A recent BE change added information about existing Jira issues to the REST endpoint. This change leverages the data and adds two main changes:
- Displays a link to an existing Jira issue
- Prevents the "Create new Jira issue" action from being shown if there is an existing issue
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
| loading state (same UX as when creating a GitLab issue) |
|---|
| Screen_Recording_2024-03-19_at_12.07.24_pm |
How to set up and validate locally
- Enable Jira integration (with issue-creation) for a project
- Run a pipeline and navigate to its security tab
- Create a Jira issue for a finding
- Verify that the loading state gets displayed as expected (same as when creating a GitLab issue)
- Verify that a new tab with the newly created Jira issue opens
- Verify that the finding for which the issue was created got updated to display a link to the issue and has the "create issue" button hidden
- Refresh the page and verify that the finding displays as expected
Related to #443630 (closed)
Edited by David Pisek