To make priorities clearer, I suggest the following changes:
- Unbreak Now! -> Do This Today!
- High -> Do within a Week
- Normal -> Do within a Month
- Low -> Do within Three Months
- Lowest -> Do within a Year
Description
Description
Related Objects
Related Objects
- Mentioned In
- T91010: Rename "Unbreak Now!" priority
- Mentioned Here
- T90360: Create a "Roadmap" project for visualisation of what's up-coming
Event Timeline
Comment Actions
I don't think this is a realistic idea. In fact, I don't think it is even desirable.
Organized teams use sprint projects and soon the Roadmap tag (T90360). About the rest, we can trust someone when takes a task, as an intention to work on it in the short term.
Nobody will promise that a low / lowest priority task will be done in 3-12 months. And besides, we have thousands of open tasks that haven't been resolved in many years, and they don't have any perspective of being solved in a few years more, if ever.
Comment Actions
The current state is:
- High - Someone is working or planning to work on this task soon.
- Normal - Less priority than High, but you are still planning to work on it.
- Low - Less priority than Normal, but you are still planning to work on it.
That is not very clear.
Comment Actions
That's fine. But what about the reporter who files a task? She should have a way to express her priority too. And what about projects that don't have sprints?
Comment Actions
A reporter can propose whatever priority in your initial description instead of the priority field. Priority is defined by whoever actually plans to work on a task, see https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities
As the proposed values in this task are highly unrealistic and can only be achieved by unlimited manpower, I am declining this task.
Feel free to reopen once you can provide sufficient manpower to fix all "Lowest" priority tasks "within a Year". :)