You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.