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'
Honestly so far this is the deal breaker for me that keeps me at Trello.
I'd even prefer to just switch the current view, so that the Lists are horizontal and the Statuses are vertical. Maybe just a different view.
That way anyone who likes it the way it is could keep the Kanban view with the Statuses running horizontal, and those of us who need more could just switch the view and use the lists instead. Frankly I'd almost prefer this - having Lists running horizontally in columns where each list has sortable statuses, so I could have the "In progress" tasks at the top, the "no progress" tasks in the middle, and the "completed" tasks out of view at the bottom.
Yes. This is important. Need to be done, doing and done are too broad. Look at Trello- https://trello.com/b/yaWmcfmG/sample-content-calendar... Sometimes it can be more than no, yes, done
By the way, <rant>I do not have a Facebook account and don't want one. Could you provide the info shared on that site to a page only logged in users can see on your own site? Zuckerburg et al have been playing fast and loose with user data and now wants government intervention to bring in regulation in/on the web. Forget him and Facebook. Put the data on your own site. I paid for it. Why should I have to go to an external site? </rant>
I have seen in many roadmaps done in trello things like to complete in this month, in 3-6 months, 1 year
The ability to establish new columns is very useful and definitively is important for many users.
Definitely agree that the need to edit/create new when it comes to task status is important. From a PM perspective, each project is different, and if the ability to create custom statuses was added, it would expand the usability of Freedcamp.
I sent a question to the support but didn't get any feedback. I guess it's my fault cause I didn't check here first...
But yeah I agree with all other opinions. Would really love to have more flexibility to implement the kanban view we want. Used Trello, Asana (and even in Github) and we alway had the freedom to define the columns.
I love Freedcamp so far, but for now I'm the only one testing it. And I think it will be really difficult to convince my team or my customers to use it.
This is a discussion - opinions exchange. Any vendor can be considered enforcing own reasoning to users, even Apple with the 1st iPhone.
Please provide your reasoning as a new comment and I will reply to you in comments.
> Thanks @David – I will revise and update status this or next week.
I did not have time to do so because we were busy with other matters here but I haven't forgotten about it.
I will also make sure we will share version 1 plan with all users contributed here and in the Facebook community group before we actually start implementing it. I am not sure if you experienced such an approach with other vendors. I personally, did not.
I can't believe the ignorant attitude towards users. Quite dissapointed. Too bad, but enforcing your own reasoning onto users' workflow is a "no go" for me.
Thanks @David - I will revise and update status this or next week. I will make it a public Wiki or a Google Doc with permission for anyone with the link to comment.
Re: Kanban - there is no difference between now and if we will also allow setting Kanban columns to be Task Lists. Right now https://blog.freedcamp.com/2016/04/27/how-advanced-subtsasks-work-in-kanban-view/
If Kanban columns will be task lists and you move subtask from task list A to B it will become a task in task list B (column)
The only way to do it properly is to design a 'flat view' where subtasks are clearly marked but they are not showing as hierarchies, I think.
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!)
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.