-
Notifications
You must be signed in to change notification settings - Fork 49
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 #5
Comments
The code scanning team is coming up with changes that will make the severities easier to understand. I'll keep you posted in Slack 👍🏼 |
On top of this Secret's should also be labeled as the Highest priority. |
There any action on this request? Would greatly benefit from it! |
Added it to our organization - https://github.com/imaware/ghas-jira-integration |
This would be great! |
github-project-automation
bot
moved this to Feature requests
in GHAS + Issue Tracking Integration Development
Aug 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like the severity of the code scanning alert (Error, Warning, Info) to map to a priority in the Jira bug that is opened.
Error = High
Warning = Medium
Info = Low
This would make it easier for product owners, scrum masters, etc to be able to prioritize the bugs they see in their backlog at a glance. This would also prevent having to look at the code scanning alerts, and match them up with the bugs. Or have to click the individual links inside the bugs to be brought to the specific alert, to then look at the severity that it has.
The text was updated successfully, but these errors were encountered: