-
Suggestion
-
Resolution: Unresolved
-
-
Jira Software
At present, Automation only supports 'Vulnerability found' as a Security trigger.
Suggested improvements{}
- Vulnerability updated
- Vulnerability closed
- "Link vulnerability to issue" action
- Support for smart values, e.g. "repository"
- Support choosing the vulnerability's status in Vulnerability found trigger
- causes
-
JRACLOUD-93122 Vulnerability status not captured by Jira's logs
-
- Gathering Impact
-
- is duplicated by
-
AUTO-1101 Suggestion for Jira Automation "Link vulnerability to issue" action. Add support for smart values in "issue to link to vulnerability" field
- Closed
-
AUTO-1123 Add "repository" smart value for security smart values
- Closed
-
AUTO-1176 Support choosing the vulnerability's status in Vulnerability found trigger
- Closed
-
AUTO-1400 Add smart value property to"Vulnerability"
- Closed
-
AUTO-1423 Allow more options for "link vulnerability to issue"
- Closed
-
AUTO-1521 Provide a trigger that checks when a vulnerability severity is updated.
- Closed
- relates to
-
JRACLOUD-92212 Vulnerabilities information via API / Automation
- Gathering Interest
[AUTO-968] More ways to work with security vulnerabilities with triggers/actions/smart values, e.g. 'Vulnerability updated'
Link | New: This issue relates to JRACLOUD-92212 [ JRACLOUD-92212 ] |
Labels | New: jsw-s10 jsw-s13 |
Component/s | New: Rule - Smart Values [ 71812 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 1017050 ] |
Link | New: This issue causes JRACLOUD-93122 [ JRACLOUD-93122 ] |
Hi ezhapa, Would you have any update about this feature? Bugs like https://jira.atlassian.com/browse/JRACLOUD-86030 have been closed and not solved. Problems and shortcomings haven't been addressed for 12-18 months now. Is Atlassian discontinuing the Security features?