Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE REQUEST: JIRA Priority Based on Severity, Epic, & Component(s) #60

Open
ajohnsonuship opened this issue Aug 20, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@ajohnsonuship
Copy link

ajohnsonuship commented Aug 20, 2020

Would it be possible to set the JIRA priority based on the alerts severity? That would be really cool. Also it would be fabulous if one could pass an epic ticket token, and component. And even cooler if we could pass a custom title, to allow for the tickets to stand out with a consistent title. :)

i.e.
JIRA_TITLE: Github Security Advisory for {0}
JIRA_EPIC: ABC-123
JIRA_COMPONENT(S): Security

Auto-map:
Trivial -> low severity
Minor -> moderate severity
Major -> high severity

@arnested
Copy link
Member

Pull requests are welcome 😄

Auto-mapping would need to be optional.

We have triage process where we manually set the priority after doing an evaluation of the security alert in the context of the project it's reported in.

Often what's classified as critical upstream is harmless in the context it's being used in. This allows us to focus attention on fixing the actual security issues fast and do those that are really just regular updates in a more steady and controlled setting.

@shahmanthan1209
Copy link

Similar to that. Currently alerts are pulled down as a header but is there any chance to add priority in title of alert / jira ticket?

@achton achton added the enhancement New feature or request label Jun 10, 2022
@akskustomer
Copy link

@achton Is anyone working on this enhancement?

@kasperg
Copy link
Member

kasperg commented Sep 18, 2023

@akskustomer No, but pull requests are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

6 participants