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 All,
I updated the concept and published http://bit.ly/2uvRsKy
Please feel free to join FB community and post your feedback here or on FB – here is a direct link – http://bit.ly/38ZfmNG
Cheers,
Igor
137 comments
-
@Scott - have you checked - https://www.dropbox.com/s/4dtvporv9mlvgu9/multiple%20statuses.png?dl=0 This is what THIS portal provides (UserVoice)? Kind of status categories wherev YOU as a user define what you want to be the options in each.
In you case you will decide if you want to create "Not approved" in "No Progress" category or you will just use "In Progress" in "Doing" and reassign back to developer who will be notified and read supposedly last comment as what was missed and needs fixing. Just a matter if you want to see "Not approved" tasks while their status as such and no one started working on it again and put it to "In Progress".
You will decide if "In Review" has to be in "Done" or "In Progress". It is totally flexible and up to you.
In systems like Jira you can spend some time and define full workflow as to what happens if a task is approved or rejected etc.
-
Scott C. Lemon commented
Here is my issue with the list that you have provided.
What occurs when a user moves a task from Doing/In Progress to Done/In Review ... and the creator/stakeholder rejects the status as they feel it is not done properly. What status are you suggesting they move the task back into?
Would it go back to No Progress/Ready to start? Since the developer might not be able to immediately go back to the task?
Or it's to go to Doing/InProgress? Even though the developer might not actually return to the task immediately?
We could make this work ... but I'm curious your thoughts on the design of this flow ...
-
-
If we add separate statuses - we will have to redo a LOT - Kanban to support 6-8 columns, List view etc etc.
What if we will do the same UserVoice does - https://www.dropbox.com/s/4dtvporv9mlvgu9/multiple%20statuses.png?dl=0
we will keep 3 statuses - Not Started, Doing, Done and allow you guys to create 2-5 sub-statuses.No Progress
In Planning
In Review
Ready to startDoing
In Progress
Delayed
Blocked
PendingDone
Cancelled
Duplicate
Completed
In ReviewSo we stay in 3 main statuses but give you options to decide if 'Delayed; is in 'Doing' category for you or in 'No Progress'
Cheers,
Igor -
If we add separate statuses - we will have to redo a LOT - Kanban to support 6-8 columns, List view etc etc.
What if we will do the same UserVoice does - https://www.dropbox.com/s/4dtvporv9mlvgu9/multiple%20statuses.png?dl=0
we will keep 3 statuses - Not Started, Doing, Done and allow you guys to create 2-5 sub-statuses.No Progress
In Planning
In Review
Ready to startDoing
In Progress
Delayed
Blocked
PendingDone
Cancelled
Duplicate
Completed
In ReviewSo we stay in 3 main statuses but give you options to decide if 'Delayed; is in 'Doing' category for you or in 'No Progress'
Cheers,
Igor -
Leesa commented
Hi Igor
Any update on this a few months later? Would be keen to know if this is in the works and when it may be available. Am finding I need this feature more and more now.
Thanks! :) -
Filipe commented
I just need one column.. In review.
-
jos bults commented
What I do now is use groups for the different statuses, but that is an entirely manual way of dealing with it. And it's prone to mistakes and omissions. (Beside that it's horribly slow).
I'm now dealing with 80 projects...
IMHO: 12 freely to define statuses - labels.
We use:
NEW
QUOTED
SAMPLE
ORDERED
INVOICED
DOWNPAID
PAID
DECLINED
FINISHED -
mealnie commented
I think it would be great to have more options too, like "approved", "refused", "pending"..
-
Андрей commented
Hi, it wold cool to add colored marks with optional name for tasks and(or) groups (5 color for 5 pennons and 5 optional names)
-
Sorry - no update.
Team is busy - some code, some provide support, some talk to investors and some close sponsorship deals with our business users to have funds to keep moving forward - http://blog.freedcamp.com/2015/11/25/sponsor-feature-development-get-freedcamp-life-time-free-with-unlimited-storage/ faster.
Igor
-
Anonymous commented
Hi Igor - Any update on adding sub-statuses or allowing a more traditional Kanban style board?
Thanks
-
Philip commented
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.
Zarina
-
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! -
Corby commented
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.
-
@Greg,
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?
-
Greg commented
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.
-
Rauno commented
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).
Cheers,
-Rauno.Cheers,
-Rauno. -
Dan Pedersen commented
Igor,
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.