The priority of issues indicates when the issue should be handled and when it should be resolved. There are examples of issue severity to give an idea of how a priority can be assigned.
Although severity and priority are often related, please keep in mind they are different topics.
This issue has not been prioritized yet.
Commit what you are working on and work on fixing the issue right now.
There should not be any unaddressed critical issue after 24 hours.
- Production website can not run.
- Development or testing work are blocked.
- All users can’t use one of the features.
Finish the task presently assigned to you, commit, then work on the issue.
There should not be any unaddressed high priority issue after 48 hours.
- Functionality or performance are severly impacted.
- A certain type of users can’t use one of the features.
Finish your story, commit, but don’t start any new story before this issue is fixed.
There should not be any unaddressed normal issue at the end of the sprint. Unless the time to address an issue exceeds the time left in the sprint
- Functionality or performance are impacted.
- A certain type of users can’t use one of the features, but with low impact on revenue.
These issues will be handled in backlog’s order and don’t need any specific attention.
- Some colors or texts are not as they should be.
- A problem impacts very specific users without impacting usage of the features.