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'
Custom Statuses for tasks – beta testing is open now.
To enable it for your account and your projects and users you need to be on our Business or Enterprise plans or their equivalents. Please contact us as shown in the attached picture to help us to process your requests faster.
Please check documentation – https://freedcamp.com/Freedcamp_LxR/Freedcamp_Devel_yOf/wiki/wiki_public/view/Espab after getting access especially if you will be applying custom statuses to your existing projects.
Hi Igor - Any update on adding sub-statuses or allowing a more traditional Kanban style board?
My company would use additional status options primarily for a review process.
This is how we would envision the status interface to be like.
An "on hold" feature
Our due dates fluctuate all the time. The project still exists but there is no set due date so we don't want to mark it as complete but we also don't want it look like we haven't finished it. So a task would be: not started, in progress, complete, on hold.
Hugo Santos commented
Would be great to have the ability to create custom 'to-do' statuses.
I am a teacher on digital project management.
Different industries, different jobs, pretty much everything has a different workflow. Now we can abstract it and make it sort-of 'one-size-fits-all' but that sometimes just ends up being more confusing/alienating than anything.
You can find workflow design tools, like the one on Jira, and other project management tools. If we could have that, now that would be fantastic!
I totally agree that an option 'For Testing' is needed. As a developer I mark something as complete, but until the managers in the company test the issue stays open.
I don't know any platform where we can escrow your money until we reach a target budget we can definitely set allowing us to work on it.
Asking to commit money in principal does not work. When you need money - people left or not interested any more.
On platforms like Kickstarter 20% is lost as commission.
I would prefer to work with one company, one Freedcamp client who will get life time free account with unlimited storage and whose name as a sponsor with a short plug will always be displayed on a marketplace page where we will ask users to go to sponsor's social pages and say 'thank you' to them.
The only idea I have is to create own page and use storage yearly subscriptions as a voting mechanism.
Let's say this feature will be developed if we collect $4K.
You vote by buying Freedcamp file storage for one year and in fact you get it for exactly one year.
We have to decide for how long we collect money for a feature - I propose 1 year.
If we collect $4K - we post delivery date and start development
If we do not collect $4K - we email everyone who contributed asking if they want to wait another year or want a refund. People who will agree to wait will get next year file storage they bough 100% free.
People who decided to take their money back will be 100% refunded. We loose always some fees when we charge you and when we refund you but we can not totally avoid it.
What do you think?
How much are we talking, sponsor-wise? I definitely couldn't individually be a sponsor but if there was some kind of "Contribute to development of this idea" feature here I'd happily spot y'all some cash. I'll look into upgrading my space but it'd be nice to know that my money was going towards a feature that I'd use.
I would love to see "Not Started / Proposed". It would be very helpful when planning what will go to "In Progress" next.
Having customizable sub-statuses would be the best way to achieve above - I think.
There is a comment below about using Task Groups to indicate status. In my mind Task Groups are about organizing the work into different sub-projects and work areas. They are not for status information. Status should be indicated by Not Started / In Progress / Completed (and their sub-statuses).
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)
Please allow us to set custom colors (RGB, HEX or CMYK) by project or project group and then sort by color. Otherwise, the color-coding in the to-do lists are meaningless.
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?