Can you use the simplified workflow on a kanban board for a project that uses a specified workflow in Jira?

I'm looking to implement a kanban board for backlog grooming. We currently use Jira for active sprints and have a specified workflow so that all tasks flow through the workflow as needed.

What I'd like to do is import this project into my Kanban board (filtering so it only displays the "Not Yet Started" tasks) and be able to apply the simplifed workflow so I can manually move them through the various stages of backlog review. I won't be changing any statuses on the tasks, as I'd like to reserve those for when these tasks are actually being worked on in a sprint by a developer.

Is it possible to apply the simplified workflow to a project in a kanban board, but have it still use the default workflow in Jira?



1 answer

1 accepted

The concept of the Simplified Workflow in GreenHopper is to provide an easier management for agile teams in their daily scrum management. However, the workflows in GreenHopper are tied to the JIRA architecture; much like how projects, screen, fields etc are.

Hence, you can only choose one workflow for a project and the Kanban board. I believe you can further modify your workflow for your backlogged items to have variable transitions for your backlog grooming sessions.

Thanks, Justin. Do you know where I can find more information on the variable transitions for backlog grooming purposes?

I don't think that the transitions are there in JIRA as a default; you would have to create them manually to your workflow and map these transitions to the steps and statuses (might need to create new ones on this as well).

Here's how I visualize the backlog grooming process. I created the following workflow that would assist me in my product backlogs:

The statuses and steps are created in order to utilize two things: the Kanban board (planning porcess) and Scrum board (development process). Hence, it is important to configure the workflow transitions accordingly.

Once the above has been done, I further create and configure a Kanban board:

Any new stories would definitely be in open status, so once it is ready for grooming, the Scrum Master would then move this to the middle column and allow the team to groom the stories.

Finally, when the stories are groomed and ready for development, they can then be planned for upcoming sprints.

For development, I would just use the Scrum board:

Notice that all the issues that are ready for sprint planning are shown in the backlog. Now I've placed three stories that are ready for development. To configure the Scrum board, the statuses need to be mapped to their respective columns:

And once this has been done, the Work section of the Scrum board would look like this:

The example I've provided may be a bit rough off the edges, but I believe that this is a basic outline for a backlog and scrum team. Hopefully, this would help a bit in your design for backlog grooming in JIRA + GH.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,944 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you