Fine, just do it please quickly.

I think it should be simple as SCRUM. And to let the user edit the headers. This way we can simplify and adjust to our workflow. I can say that many PM apps are starting to include Kanban boards because AGILILITY is on the rise.

From my view, i would make a project for every sprint since freedcamp is not really setup for SCRUM. But ideally, having access to the product backlog is useful for planning.

IDEAL

Column 1
Product Backlog

Column 2
Sprint Backlog

Column 3
In progress

Column 4
In Review

Column 5
Done or Retrospective

A suggestion: the ability to make your own activity or workflow pipeline in order to track progress for a specific process. For example we as a recruitment company after the candidate qualification we have steps that need to be taken, in order to say that a candidate has gone through the full process.

In short the ability to create a custom kanban with more options inbetween and several steps before it is placed in the last box as completed.Thus creating a pipeline process to your own liking and adding the name of the kandidate to the pipeline to see what steps are still left.

This ability to create your own custom kanban board it will allow for more possibilities and tracking of activities by object.

Thank you

Yes - looks like we MAY have to go with custom statuses with no hierarchy and allow as many columns as you want. We only need to ask order of them and what statuses mean progress, no progress or completion. If you want to put completion on left and not started statuses on right - it is up to you.

Igor@freedcamp.com

+1 for custom statuses. You would create new status and choose which kanban column it goes in, plus icon and colour. Dragging into a kanban column would need to prompt for status, or else you could have a default status for each column (which would basically be the status hierarchy which was proposed). Or do like jira and show different status options in different regions of the column. This would avoid a long list of presets which people might not need, and allow users to create exactly the status options which are required for the project.

@Wayne - with this approach we can stay within 3 columns and allow fully custom statuses.

It does not stop us from allowing all your statuses to be columns but we can do it LATER.

Proposed here solution is MVP to allow more statuses without redoing a lot in Freedcamp. Shortest path for it to be done and released.

As for departments being able to act as statuses - probably better to use it this way - https://www.dropbox.com/s/vfet3uwizdqxstr/Kanban%203%20columns%20workaround.png?dl=0

but looks like you do not need - not completed, in progress and completed statuses in each department.

Have you considered Trello at all? If you only push tasks between manufacturing process columns and each person responsible for a step is to grab as many top tasks as possible, do them and move them to next step - looks like Trello will work better for you.

Until we will implement this and also add support multiple statuses columns in Kanban we will never be a perfect system for your workflow, unfortunately.

It sounds to me like the freedcamp methodology uses users as departments instead of creating kanban departments and assigning users to departments. this can work but a little more of a work around. still will work fine.

This can work yes. It would be beneficial if the user can custom name those subcategories. Each business is different and it would help for certain. Kanban systems are all about moving a project along a whiteboard's department columns. For example, in our business, we create a concept of something, then it goes to our engineering to be drawn, then over to manager for approval, then over to partsperson to order raw material, then comes into recieving/shipping, then goes to inspection, then goes to either machining CNC or welding, then back to Inspection, then to painting, then to marketing, then to inventory.
So if doing a kanban system you'll need to allow the user to create custom columns, however with your system of subgroups it can still work but instead of calling subcategories as sub-status names, allow the user to create custom named sub columns of department names.

Hi guys! I have one suggestion. Now in task groups, we use only three columns: "No progress", "In Progress" and "Completed". However what if i want to use more columns, four or more? Please add function which allow to add such number of columns what I want, when i create new task groups. Thanks.

I think this would be a great first step and then start planning the redo of the Kanban style to support multiple custom columns.

@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.

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 ...

+29 votes from https://freedcamp.uservoice.com/forums/126945-suggestions-for-features/suggestions/13972368-an-option-for-waiting-on-approval-as-a-workflow

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 start

Doing
In Progress
Delayed
Blocked
Pending

Done
Cancelled
Duplicate
Completed
In Review

So 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 start

Doing
In Progress
Delayed
Blocked
Pending

Done
Cancelled
Duplicate
Completed
In Review

So 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

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! :)

I just need one column.. In review.

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

I think it would be great to have more options too, like "approved", "refused", "pending"..

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