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; } } }

Switching workflow schemes gives unexpected results in migrating the issues

Sandra Meessen

Hi,

We created a complete new workflow scheme for our project and a new issue type scheme. Switching the issue type scheme works fine, but when switching the workflow scheme I run into a problem. I can only choose some of my workflow statuses in new situation, not all of them. What am I doing wrong?

Accepted answers

Jack Brickey

To be clear you are saying that you have a workflow with let’s say 5 statuses but you can only transition to say 3 of the 5. Is that correct? Are you sure you published the new workflow? Can you share a snapshot of the workflow?

All comments

Jack Brickey

Sandra Meessen

Hi Jack, Thank you for your quick reply. Yes, new workflow is active and published. I attached a screenprint of the new workflow and of the screen where I can associate my SR issues to statuses of the new workflow and where I wonder why I only see a few instead of all. Thank you for your help and regards, Sandra Associate new workflow statuses.png SR new workflow.JPG

Jack Brickey

Ok, i see so you are at the associate step where you are mapping current status to new status in the target workflow. I'm not sure TBH because I too would expect that if you are in fact looking at the target workflow then the statues should be present. I would really need to see this firsthand to better assess which isn't possible. You may need to reach out to Atlassian Support.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

workflow

status