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'
Hi! When will this be moved to a development stage? As a work around, I created various lists so when a task is completed, I move it to the new list to complete the workflow.
With this feature, I'd order 100 business licences ! :)
Sherin Sudarsanan commented
Perfect, This Feature along with the simple design and easy to understand flow, would make Freedcamp the Best. Very Nice to hear this. Customizable task status' are really useful in today's agile world.
kanban with 3 unchangeable columns is really not a kanban. It must be adjustable based on user needs
benjy rose commented
Customizable project statuses would be an extremely useful feature. Unless I'm misunderstanding, the desire to keep Statuses as No Progress / In Progress / Completed seems arbitrary, even if substatuses are allowed.
If we're thinking about extending this, then it would make much more sense to make it completely flexible and allow an infinite number of statuses which could be used as Kanban columns or Task List groupings (swim lanes).
Start with the current three statuses as defaults, but make it extensible. That's my vote.
David Jorjani commented
Hi, What's the ETA on this feature? We can't work without it anymore and really need it to be able to stay with Freedcamp.
Tamala Bradham commented
Please consider allowing us to edit the Kanban columns to other categories and the ability to add additional columns. For example, I would like to add a resource column that accompanies the project. We also have an approval process for projects and it would be good to be able to see what step in the progress the project is in without having to search each task.
"Cannot Complete" Redlining Function
I think it would be great to add a redlining function to cross off tasks that you never did or won't work but still want to be part of the thinking process.
Say one has three ideas for jelly flavors:
Out of the three, a logical person would write reports for the last two but skip the first one. While we still want to know we came up with the idea for the wrong jelly flavor but will not mark as completed since we did not write a report for that item.
Additionally, if you have a list of guests. 10 say they can come and 5 say they cannot come. There's no visual way to differentiate between the two groups if they both have to be marked as completed to get them out of the way in a green (positive) manner.
Let's not mix more statuses and more Kanban columns because these are completely different things. Unless in your workflow a task added to Testing status is immediately assumed in progress - Testing is not a status but a task list where you add a task to and someone starts testing and completes it and moved it to 'Release' task list.
However, we do want to unify how most used Freedcamp application - Tasks works.
We want to allow flexible groupings - currently tasks grouped by a task list with an option to remove groupings entirely.
Kanban view is special as you have groupings - currently task lists and columns (currently statuses). So here we can allow you to decide what attributes you want to use (if any) for grouping and what to use as columns. So you can have no grouping and task lists as columns or people as groupings and statuses as columns.
This concept is demonstrated here https://www.dropbox.com/s/gwnunq91u5hrl4i/Tasks%20Views.png?dl=0 and applies to all views - List, Kanban and Gantt with the exception that Kanban will also allow to define what to use as columns.
Once this is done - it will cover most use cases and we will only implement substatuses - an ability to define 'Blocked', 'Waiting response' as a substatuses for 'No Progress' status and ability to expose substatuses as columns and groupings. We would like to keep them as substatuses as we know semantics which is only split into 3 things - not doing, doing and done so we can use it in Freedcamp to help you complete your projects faster.
Let us know what you think in the comments, please!
Ernesto Flames commented
Yes please, more kanban columns!... For example, in my job we are using this structure:
- Backlog (to store all epics and ideas) only the project admin can edit them
- To do (Freedcamp not in progress column)
- In progress (Freedcamp in progress column)
- UAT - Task done but waiting for user testing or waiting for approval
- Ready for PRD - Accepted by user and waiting for implementation
- Done - Task has been implemented in production.
Yes, too many but we are a large development team, would be a nice improve of Freedcamp man!!.. hehe and sorry for my english by the way.
Jim Bob commented
Would like to know when this planned feature is in because it's the only thing stopping me from using Freed Camp, Ora.pm has the best Kaban board out there, learn from them.
@Mike - all 3 main statuses will have custom sub-statuses. Right now you can use Custom Fields and add extra d/down "Sub-status":
No Progress - Planned
No Progress - Waiting for Approval
No Progress - Delayed
In Progress - Testing
In Progress - Review
Completed - Declined
Custom Fields, once used, are exposed to filters so you can easily use them to create your most needed filters and switch contexts quickly.
See here for details - https://freedcamp.com/Freedcamp_LxR/Freedcamp_Devel_yOf/wiki/wiki_public/view/3Tbab
It is part of Freedcamp Business
I frankly agree w/ the Freedcamp position that the three states are sufficient *if* (and only if) those states can have substates. Being able to sort/filter at the two levels seems very valuable to me.
Note that even "Completed" needs possible substates... for example, I have tasks that are decided against (never completed, or perhaps even started) due to changing environment. I don't want to delete them for historical reasons, but marking them Complete is not right either. I'd like a Completed substate of "Abandoned" or similar.
PS: I'm currently on free... keep planning to upgrade to paid plan but have never pulled the trigger... this change would definitely push me into action :-)
Do you agree with an action plan provided in the latest status update? Are you planning to go with one of our premium plans or only interested in the free plan? You can contact me email@example.com.
So this has been in the pipeline for nearly 4 years now? This is the only feature I'm waiting for to bring my team onboard. I'm assuming it's not happening anytime soon?
That one thing - lack of statuses want me to make my own Task management for my needs... Freedcamp lacks alot for my management needs, but is enough if I use it as task management... if not those statuses. It would be real life saver!
Why in this case 5 task lists with the following names won't work?
You move your tasks from Backlog where all tasks are always not in progress status to Analysis task list, assign and start it. When a task in Analysis is completed you push them to Development task list etc.
You can also add Custom Field 'Stage' as a drop down and have all your tasks having one of these attributes attached:
if you are on Business Plan.
Hi Feedback squad; no this isn't what I meant.
You would essentially define your own values for a picklist of progress stages; e.g/:
Default (at present) for any task is:
2. In Progress
But I could instead define stages as:
2. Analysis started
3. Analysis complete
4. Development started
5. Development complete
6. Testing started
7. Testing complete
8. Deployment Ready
So my apologies maybe not max 7; but hopefully you get my drift....
I assume each of 7 statuses will have a binary attribute attached (in progress, not in progress) and order of these statuses needs to be defined as well by you.
Every business has different language for stages of dev/non-dev project stages.
The best possible solution would be allowing a custom set of statuses to be defined (up to say max 7); then allowing users to move tasks/items through thier kanban dependent on the order of their custom statuses.
This would allow any business to use freedcamp without having to translate other existing processes/procedures - huge stepforward in the platform's key functionality.