Pipeline Security Report: Fix issue with deleted Jira issue
When a Jira issue, which was created for a security finding, gets deleted, the pipeline security dashboard throws an error and the affected finding does not get rendered:
This happens because a previous change, which added the rendering of Jira issues to the report, assumed that a certain field (external_issue_details
) will always be populated and not null
.
How to reproduce
- Create a Jira issue for a finding via the pipeline security report
- Delete that Jira issue
- Reload the security report
- The finding does not render and there is a console error
Edited by David Pisek