Skip to content

Fix #1043: use customfield_10319 as default severity field #1051

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

Merged
merged 1 commit into from
Sep 17, 2024

Conversation

leplatrem
Copy link
Contributor

Fix #1043

From Jira admin:

Note: these have two separate field names.
* customfield_10716 is “Requested Severity Level”
* customfield_10319 is “Severity ” (with the space at the end of Severity
We’ll be working on removing additional trailing spaces and duplicates in our cleanup, but these two custom fields have separate names

@leplatrem leplatrem requested a review from a team as a code owner September 17, 2024 07:56
@leplatrem leplatrem added the enhancement New feature or request label Sep 17, 2024
@github-actions github-actions bot added the configuration Changes to JBI action configuration label Sep 17, 2024
@leplatrem leplatrem merged commit dd99e45 into main Sep 17, 2024
8 of 9 checks passed
@leplatrem leplatrem deleted the use-other-severity-field-by-default branch September 17, 2024 14:05
davehunt pushed a commit to davehunt/jira-bugzilla-integration that referenced this pull request Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration Changes to JBI action configuration enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate default Severity field
2 participants