User-Defined Status/Stages
Presently, to define status of a task, there are only three options available with the user, namely, Not Started, In Progress, Complete.
Provision to user's to create more status-tags will help track the status.
Anonymous
shared this idea
27 comments
-
Lutz
commented
Absolute essential to have that!!!
-
Anonymous
commented
Having only three task status is very limiting. We need additional statuses of 'In Test', 'On Hold' at a minimum but ideally we should have the ability to create our own status levels.
-
Didier Van den Meersschaut
commented
This should be part of next release. It is a rather simple thing, with great benefits. And it does not harm the business case of project online.
-
Peter Kaintz
commented
This would be a very nice improvement for us.
-
Ryan Robinson
commented
This is a big request for us, as there might also be statuses like waiting for an answer from a client, which is different than in progress.
-
Steven Brazzell
commented
Definitely a needed addition, would make it an even better alternative to Jira.
-
Anonymous
commented
Seems like this would be a quick implementation. Any reason they haven't done this yet or what a timeline might be (original idea was december 2016)
-
Merethe Stave
commented
Or, at least add a status = On hold/awaiting 3rd party, as sometimes tasks are not possible to do, but still want to keep them in the list for when it is possible, eg. when tasks is currently out of scope, or depended on someone/something else to be completed.
Or, if not open for customization, at least give some options to choose from (eg. as mentioned in previous comments; "pending", "test", etc. -
Anonymous
commented
Ability to assign a Task to multiple People with a Checkbox "Everybody has to do the Task".
If unchecked: Task is done, when somebody did it, if checked, Task is done, if everybody did it... -
Simon Tocker commented
We would have loads of extra status codes, in one instance, as there are multiple stages in our pipeline, including the usual blocked, in test, in uat, etc all belong in that "centre" section of a kanban
-
Matthias
commented
Absolutely agree. To use planner as kanban in a useful way, at least two additional states are needed. As already mentioned "verify" and "backlog" would be very helpful.
-
Andy Wagg
commented
Yes, would like to have tasks in Warranty
-
Jacco Walbeek
commented
Absolutely. We want to have tasks in 'test' and 'waiting'
-
Anonymous
commented
I agree. At minimum an additional status i.e. "pending" or "waiting" would be very helpful for an effective kanban style plan. Of course fully customisation would be the perfect solution.
-
Anonymous
commented
I'd like this too - even a couple of customizable statuses to be able to add a bit more flexibility
-
Tony
commented
We definitely need that. Important new status are: Waiting for, Backlog...
-
Jim Cooley
commented
Great idea, way too limiting as is.
-
Miroslav Milutinovic
commented
We would need this also!
-
Sandra Soniec
commented
Absolutely must have
-
Norm Sash
commented
Yep, I want the flexibility of user-defined status. I know there are other suggestions for Planner about this, but they all seem to be for adding a specific status, so I didn't vote for those ideas. Rather, I'm voting for this idea to give us user defined status just like we can have user defined buckets.