What is it?
Manuscript uses a “Priority” system but other issue trackers often opt for “Severity,” or even a hybrid of both. Priority represents the importance of fixing a bug, and reflects a business decision as to how soon that bug should be fixed: all priority 1 bugs should be fixed before priority 2 bugs, and so on. Severity represents “how bad a bug is”.
Who will use it?
All type of users who have access to manuscript and are working on their cases.
How is it used?
The best way to use priorities is to have a single, global priority scheme across all your projects, bugs, and features so that every team member can always work down their list of cases in order of priority.
To change the labels:
1. Log on as an administrator
2. Click on the Admin menu and choose Priority
Here is a typical scheme you might use:
1. Life or death emergency… the roof is actually on fire. Drop everything and fix.
2. A customer is waiting for this to be completed.
3. Very important
5. Not so important – fix if time
6. Probably won’t fix but worth remembering
7. Do not fix
The Evidence-Based Scheduling reports assume that you are going to implement features in order of priority, and they can show you different schedules based on how many priorities you choose to do. Assuming you have estimates, it will let you see how much it would affect your schedule to do those “fix if time” features.