Hey all,
I'm not sure if I should split this into different tickets, but here it goes.
Recently, I have migrated my Editorial Team to Kanban.
In theory, it seems simple - however, I seem to be having some problems with my workflow, which is breaking my Kanban board.
It is worth noting that my project is shared with multiple boards and delivery leads (around 6 of them, using both Scrum and Kanban).
I've broken up my columns into the following:
https://gyazo.com/6a414f8fc0c5d71860c3f984623f5f59
It is based on my diagram below:
https://gyazo.com/80268d34eb8b33994049ad4b6f27918b
However, what I have noticed is that whenever I create a task, it simply goes into 'To Do' as opposed to Backlog, where we want to run check's to ensure it is actually ready to be worked on.
From this I figured I would need to ultimately update our Workflow so that it comes before To Do - am I right?
Here is a screen of our workflow:
https://gyazo.com/5d4e5b757f9634d8dc6d067fc74f6e2d
What I also figured was that to match my diagram above, I would have to alter our workflow accordingly, which would mean that it would change all the board's flow wouldn't it? As you can't have different workflows on the same Profect can you?
Any help would be hugely appreciated :)
Cheers,
Josh
Hello @Joshua Buchanan
The simple answer is that when you create an issue it will automatically go to the Status from the workflow designated by the Create transition. That is the transition between the gray dot and a status. Looking at you diagram you would need to change the target of the Create transition from the To Do status to the Backlog status.
Workflows are applied to projects through Workflow Schemes. Through a Workflow Scheme you can have multiple workflows that apply to a single project, by configuring workflows to apply to specific issue types in the project. So, you can have multiple workflows on a single project, but not multiple workflows for a single type of issue in that project.
If you have multiple boards that reference the project, then changes to the workflow(s) for that project can affect all those boards. The affect on the boards depends on the change you make and how the board is configured. A board is just a way of visualizing and working with issues in 1..n projects.
Hey Trudy,
Thanks for that - glad my thinking was there!
Yeah I figured as much - guess its back to the drawing board - thank you :)
Cheers,
Josh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.