Add severity to priority mapping support#1
Merged
arjantop-cai merged 1 commit intov1.xfrom Jan 16, 2026
Merged
Conversation
Add support for mapping Dependabot severity levels (CRITICAL, HIGH, MODERATE, LOW) to Jira priority values via environment variables: - JIRA_PRIORITY_MAPPING: Comma-separated SEVERITY:Priority pairs Example: CRITICAL:P0,HIGH:P1,MODERATE:P2,LOW:P3 - JIRA_PRIORITY_DEFAULT: Fallback priority when severity not in mapping This allows automatic prioritization of security tickets based on vulnerability severity. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
uh-cookie
approved these changes
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for mapping Dependabot severity levels (CRITICAL, HIGH, MODERATE, LOW) to Jira priority values via environment variables:
Example: CRITICAL:P0,HIGH:P1,MODERATE:P2,LOW:P3
This allows automatic prioritization of security tickets based on vulnerability severity.