nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transitions from workflow to workflow

Anis Ahmed Choh1

Hi All,

We have two work flows, one called "Backlog workflow" we have Epics and Stories created, in this flow we groom the stories and get them invested this is the process of creating stories, sub-tasks etc...

Once they are invested we pick what we want from our Invested status and want to move them into our "Development workflow".

How would I go about doing this. Is this possible?

Kind Regards,

Anis Ahmed Chohan

Accepted answers

Alan Corey1

I have done this before with two boards. One Kanban Board for "pre-development" and one Scrum board for "development."

The Kanban board is filtered to only show pre-dev statuses like "To Do", "Needs Requirements", "Needs Sizing" and then the last column/status is "Sprint Ready".

The Scrum board then filters out all those statuses except for "Sprint Ready" and has all item statuses of "Sprint Ready" as it's backlog.

All comments

Nic Brough -Adaptavist-

The correct solution here is to stop trying to use two workflows. You've got one process, define that as the workflow.

Your other options are

Have two projects, one for backlog, one for development.
Have two issue types, one for backlog, one for development.

When you pick stuff to move it from backlog to development, you move it from one project or issue-type to the other.

Anis Ahmed Choh1

The issue with that is, when we raise bugs they get put into our initial state and go straight into backlog, when we want them to go into our develop to do status.

Nic Brough -Adaptavist-

Ok, change the workflow for bugs so that it lands in "to do" instead of whatever you have in backlog.

Anis Ahmed Choh1

Is there a plugin that might deal with this? Or is there a way to hold sub-tasks, stories from going into sprint if there epic isn't in a certain status?

Alan Corey1

I have done this before with two boards. One Kanban Board for "pre-development" and one Scrum board for "development."

The Kanban board is filtered to only show pre-dev statuses like "To Do", "Needs Requirements", "Needs Sizing" and then the last column/status is "Sprint Ready".

The Scrum board then filters out all those statuses except for "Sprint Ready" and has all item statuses of "Sprint Ready" as it's backlog.

Nic Brough -Adaptavist-

Yes, one workflow, but more than one way to look at it, showing only the issues in the relevant status. I should have said that, so thanks for adding it!

Anis Ahmed Choh1

Yes brilliant! This works beautifully! I ended up to this conclusion I have multiple scrum boards to show the progress of tickets now .

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud