Issue updated
Description: High priority and low impact ... => High priority and low impact ...
Add implied ranking field to ITS
High priority and low impact can and should be quickly fixed whereas low priority and high impact will end up lower on the list. With this in mind a "ranking" can be determined using the priority and impact fields (similar to the risk score in the Procon plugin).
Priority scores:
- High
- Medium
- Low
Impact score:
- Low
- Medium
- High
Ranking = Priority score + Impact score - 1
Examples:
1 = High priority + Low impact
2 = High priority + Medium impact
2 = Medium priority + Low impact
3 = High priority + High impact
3 = Medium priority + Medium impact
3 = Low priority + Low impact
4 = Medium priority + High impact
4 = Low priority + Medium impact
5 = Low priority + High impact
2 = High priority + Medium impact
2 = Medium priority + Low impact
3 = High priority + High impact
3 = Medium priority + Medium impact
3 = Low priority + Low impact
4 = Medium priority + High impact
4 = Low priority + Medium impact
5 = Low priority + High impact
Updates (2)
Saturday 13th of June 2015 at 15:55
:
Monday 15th of June 2015 at 14:09
:
Issue updated
Workflow: Open => Closed
Fixed in changeset: 0 => 49
Workflow: Open => Closed
Fixed in changeset: 0 => 49
