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 scheme caused issues with board status. Can it be fixed?

Gil_2dvf2c

Hi.

We have a project that started 1.5 years ago with an old workflow.

I created a new workflow per issue type and I used it on a dummy project for testing.

Now I would like to use this new workflow on the existing project.

I finalised the Cloud Backup option, and currently I'm out of office hours, so it should be a good time to switch the workflow.

However, before I proceed, I'd like to know if anyone can recommend on some practices to perform before I switch to the new workflow?

This project has also new screens schemes and new field schemes per issue type, but I would like to start with the migration of the workflow first.

Thanks.

Accepted answers

All comments

Alexey Matveev

Hello,

I have not done any preliminary tasks before switching a workflow. If some issues must be migrated to new statuses. then you will be asked to provide new statuses for such issues. That is all.

Gil_2dvf2c

actually, I have encountered issues

"this status is not available in any of the workflows used by this board."

This is not true. These statuses are used in the new workflow.

Before the switch to the new scheme, I did map the issues to their new status.

Can I fix this?

Alexey Matveev

You should map statuses in the board after you migrated to new workflow

Gil_2dvf2c

This is not possible since Jira is asking to map to statuses available in the new workflow prior to initiating the migration.

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

workflow