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.
How do you handle the migration of issues to the new workflow?
I thought that handling this is done when Jira is asking to map the old status to the new status of the workflow I'm migrating to.
Besides that, I'm not sure what else can be done aside from tweaking the project's JQL.
yes, that wasn't a given.
For the JQL:
project = project AND status not in (Rejected)AND (sprint in openSprints() OR sprint in futureSprints() OR sprint = EMPTY OR issuetype = Epic)
I had to remove: OR issuetype = Epic
I'm not sure why this is the case, but it seems to resolve most of it.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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