0000299: Priority management

Description

We need to start managing priorities in Mantis.
Severity expresses the impact of the issue from a user point of view.
Priority expresses the order in which issues should be tackled.

To properly manage priorities:
1) All new non-critical issues should have normal priority and the reporter should not be able to change that.
2) Critical issues should have immediate priority by default
3) The triage team should set the priority when confirming or scheduling a bug; this should be part of the normal workflow.
4) Developers should have the ability to update priority, although this is not part of the normal workflow..
5) An automated process should automatically increase the priority of older defects to prevent them from becoming stale (i.e. every 60 days, increase priority by one level). This does not apply to feature requests (or perhaps it does with a much lower speed)

Steps To Reproduce

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

has duplicate

feature request

0000428

closed

When issue severity is set to critical, priority should be set to immediate

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2008-05-14 07:42	pjuvara	New Issue
2008-05-14 07:42	pjuvara	Assigned To	=> admin
2008-05-14 17:22	jaimetorre	Assigned To	admin => jaimetorre
2008-05-23 09:25	jaimetorre	Status	new => scheduled
2008-05-26 12:18	pjuvara	Relationship added	has duplicate 0000428
2009-11-19 09:29	jpabloae	Assigned To	jaimetorre => jpabloae
2011-08-24 12:58	jpabloae	Assigned To	jpabloae => gorka_gil
2018-04-06 17:59	shuehner	Status	scheduled => closed
2018-04-06 17:59	shuehner	Resolution	open => out of date