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'
David M. commented
I would say I also disagree with the notion that something can only be "No Progress", "In Progress", and "Done".
This is partly semantics, but in my book, as someone else alluded, the notion that something can be "In Progress" would be contradictory to saying it is also "Paused", "Blocked", "Waiting", etc. - terms which decidedly mean something is NOT MAKING "progress".
Perhaps changing the term "In Progress" to "Started" would be more in line with your meaning, and resolve that conflict, and allow the substatuses mentioned to make more sense. But all told, still I think this is needlessly restrictive, and misaligned with what so many tools offer.
By your seeming definition, one could argue that your "In Progress" status is superfluous - one could just as well indicate that something has ever begun by filling in the Start Date (ever).
I have a requirement to generate a report (from the data feed) of what was worked on in the past week, and without a way to indicate that something that had been started prior to that period had been paused in some way, I don't see a way to do that with the existing status values. Reverting back to "No Progress" is certainly nonsensical, as well.
If allowing more status values causes problems in other portions of your system because they are interpreting the Status value (rather than just showing it or filtering by it), perhaps you could retain the two endpoints of your tripartite state ('No Progress' and 'Done') as reserved, and any place where you had previously keyed on "In Progress" change the implementation to be "NOT 'No Progress' AND not 'Done', then allowing other user-defined values to be inserted "in-between" those two.
David M. commented
I haven't read all of the comments to know if this is addressed, but if Kanban phases are implemented with different task lists, then that would seem to mean that tasks cannot be hierarchical. Moving a subtask to a different Kanban phase will remove it as a subtask of its parent in the original phase list.
Losing those task relationships would be bad for our project.
Maybe allow Kanban phases to be driven by a Custom Field (for those that don't like the other two options?)
Niels Anders commented
Without more status options this application is quite useless to software engineers like me. I can't see which tasks are ready for review/testing or whatever without looking into comments. I used to work with TargetProcess which was much more convenient.
I disagree with freedcamps analysis on "in progress", while yes theoretically the sub task idea would make sense, however.. when developing software or working on large projects multiple statuses in kanban are appropriate. Matter of fact this is the only software I have ever used where there is only three statuses that cannot be broken out into a kanban.. For those needing more robust kanbans I recommend clickup or smartsheet. This problem of not listening to user feedback is why I will not be subscribing (even though I like a lot of the other features)
Rob Sorrell commented
I agree with those who say there should be more status options. I waste so much time coming back to software and having to go through all the individual comments on each task to find out what needs reviewing and what is still being worked on. "In Progress" is far too broad a term. For example a review of the site that we are working on could find many issues that need rectifying. Some on these issues may be completed and then require checking and testing, some may be more troublesome and need more work. Both are "In progress" until they have been signed off but there is no way to see where each one is. This is a genuine issue for me and one which I may need to move to a different service when my staff numbers expand. I think Monday offer more.
Some people's workflows are just a matter of the team that formed. I'm the software owner, and also providing Software Quality Assurance and Testing. I'd like the visual of having things moved into an "Awaiting Testing" column so I can see tasks that are ready for me, and then I can either comment and return to In Progress, or move to Complete. Is there an ETA for this, or should I just plan on living with what Freedcamp has (which I'm enjoying using by the way!)
Edward Apostol commented
Is there anything that is going to be done about kanban board customization? This thread has been around since 2016. three years.
I can understand the idea that Testing might be a task (subtask) and not a status. But there's a world of difference between No Progress and Blocked (No Progress Possible). It seems like adding Blocked is a lot simpler than adding task dependencies.
Any chance there's an update on this?
yannick armspach commented
'we plan to allow to switch Kanban view to show columns as task lists' always under develeopement ?
Dustin Bauman commented
It would be great to be able to modify the status, like Review, Pending or others.
What’s the latest?
Can you share the status? it will really help to have this
Looking for an update on this feature, we need to have control of the Kanban naming of columns, everyone has a different workflow and different internal systems, Freedcamp needs to understand and adapt to workflows, not the other way around. Thank you.
Any update on implementation?
This is such a simple, yet major decision changing feature.
any progress on this?
Even if this sounds minimal or arbitrary to Igor and Freedcamp, I cannot persuade my team to use this software until given full control of columns/statuses/lists/Kanban or whatever you want to call them. I don't think "sub-statuses" will cut it either.
Yes - I am desperately waiting for this.... I have even started looking at other solutions.
@Diamond - semantically 'yes' it is either in progress, not in progress or completed. In progress status can be 'Testing', no progress status can be 'On Hold' or 'Blocked'.
Kanban columns are not equal to task statuses. We have this posting here really about two different things
- I want to call my statuses to give them different names such as 'Testing', 'On Hold' or 'Blocked'. If you want to create a new status you will need to tell the system if Testing is one of - doing, not doing or done so Freedcamp knows when you will want to see all tasks 'doing' to be filtered and for many other things
- I want more Kanban columns - the obvious solution here is to allow to define what Kanban columns are (task lists, people, statuses or priorities). If you create task list 'Test' and set your Kanban to use task lists as columns you will see column 'Test'.
I personally (igorfree..com) think that 'Test' is not a status. It can be a task list or a tag. 'Test' semantically does not tell you if it is ready for testing, in testing or completed testing, so cannot act as a status but with the first bullet point - sure you can set it as a status if you want, but will have to define if it status semantically tied to not doing, doing or done.
So no - we do not want to tell anyone what to do. Two bullet points I outlined provide enough room for you to create as many Kanban columns but do even more - set columns to be task lists and group by a person, priority, due date (currently Kanban is always statuses for columns and task lists for grouping).
"We think that each task can be only in progress..."??? Seriously??? You're going to tell me how I should organize my projects?!? How about: "the customer wants". I want the ability to create as many customizable Kanban columns as I think is needed for my project. Until this happens, I'll continue to use Asana.