In JIIRA, we have only Priority field while raising tickets. But that is becoming more difficult for the developers to fix issues if there are like 100 medium priority issues and without knowing severity levels, its time consuming and non productive
Add a new custom field to capture "Severity".
Oddly, Severity is one of the reasons Jira was written - developers were simply ignoring it because it was so rarely set usefully by end users, Mike and Scott deliberately dropped it.
I tend to prefer driving priority and ranking by severity and impact, with severity being a "level of bad you see" (with human descriptions from "minor cosmetic error" through "it breaks stuff a lot, but is still usable" through to "system unusable"), and the impact giving you an idea of the users affected. An issue that is "system unusable" but for one person is high severity, low impact and hence quite a low priority compared with "it breaks a lot" for 10,000 people.
As part of Atlassian's commitment to combat climate change, we will run our operations on 100 percent renewable energy by 2025. We’re also setting science-based targets to limit warming to 1.5°C and ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events