Tasks - more Progress Status Types
It will be great if you add task statuses different than 'in progress' and 'closed' i.e. we are software company that have different workflow:
'not started', 'in progress', 'done', 'for testing', 'competed', 'archived'
Dan Pedersen commented
The proposed state would be better than planned.
Using a status field would provement. My major issue today, is the absence of in-testing and release to production states. But, by using using the state filters I loose the ability to see everything at one time. The beauty of Kanban is its visual simplification results in improved processes, improved communication and improved performance.
If someone added 12 columns, they did not understand Kanban. Kanban should be limited to what can be comfortably put onto one page. If you cannot put in onto one page, your process is too complex or you have too much work in-process.
My team loves the simplicity of your tool. Thank you for your prompt response.
Feel free to contact me directly.
I actually think that it will be more productive not to decide on sub-status names but give you a reasonable amount of spots - say up to 10 and let you decide which ones you need and how they relate to main statuses.
Some will use 5 spots to have sub-statuses for 'No Progress', 2 - 'In Progress' and 2 for 'Completed' some will decide to use them differently.
Main point here:
- we do not enforce sub-status names as all projects require different ones
- we give you enough spots - 10
- sub-statuses should be easy to copy when a new project is created from an existing project
- tasks can have a status with no sub-status
- sub-statuses can be added, removed and edited after project was created.
Posting feedback from a client I got in support here:
No Progress/On Hold
In Progress/Pending Response
Would be helpful.
Even better would be:
In Progress / Pending Approval
Sub statuses are great!
I would like "Completed/Waiting for approval (sign off) Or In Progress/Waiting for approval (sign off)
Additionally, for a client facing web development projects, "stuck" for items which need client input, and "approval" which is a stage before "done" so that the client can sign off before launch
We will do more statuses in Tasks PRO version or add add-on you can drop on top of Tasks to get extra customisable statuses. Problem with a lot of our promises is under capitalisation and lack of resources to improve product faster :(
As I said before - if you love Freedcamp - pay 2$ a month for extra storage even if you do not need it to keep us going. We work very hard here to keep most of it free for you too.
I'd love to be able to put a task "on hold" but alas you can't in Freedcamp. There are multiple reasons why you need more than just stop,go and finish options but these requests have been outstanding for over a year and Igor seems to be wedded to a tagging option that doesn't appear to suit most users requests. Even some standard Prince2, PMP or ITIL options would suffice.
We are currently testing freedcamp because we are unhappy with basecamp. We looked at several tools and freedcamp made a real good impression, because it is simple and easy to use.
There is just one thing, which is major drawback, and this is the limitration of status-values. Igor proposes another approach, but this is a kind of workaround, because logically a task (to-do) has a status. If one starts to manage status with categories, it will turn out complicated. Furthermore reporting is also much easier.
What is the typcial scenario? Project manager assigns tasks to another team member. The team member completes the task, but now a review and testing is needed. Only when this step is succesful, then the task is completed.
So, we would strongly vote for having more status values. The perfect solution would be, that the the admin could define the values himself, but I guess this needs some more programm logic and time. The most easy solution would be when you just offer a few more status such as for example:
- Implementation Done
- Testing in progress
- Review in progress
Users who do not need it, simply can ignore it. And I guess you have implemented this in a few minutes by simply adding some values.
Do you use Task groups? How about creating a task group called 'Waiting for deployment' and moving tasks to it with drag and drop or by editing? We, at Freedcamp, create task groups with Sprint number - say Sprint 12 now. Completed tasks get closed, tasks requiring some SQL to be completed or configuration of the system changed - we add prefix to this task (FOR BUILD TASK) and assign this to a person upgrading app (which is me in our case).
If we add extra statuses more likely it will be a Marketplace module with a fee attached to it.
Stephen Rowe commented
I wold really like to create my own statuses. That way I could add some like "waiting deployment".
Claude Janz commented
What about a managable list?
Leighton Christiansen commented
I would also like to see an "On-hold" status. Or perhaps customizable To-DO status? Obviously with other color codes than yellow, green, and grey.
I would really like the 'ready for testing' option
Any word on when this will be completed?
I would love to create our own statuses:
- Waiting on customer
- Need more information
yes this is really useful.
the other is "rescheduled" since we don't have baselining here. it would be great if the same to do can be marked rescheduled with the older date as well.
I like this idea too
What about 'In Planning', 'Proposed'?