Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,423
Community Members
 
Community Events
184
Community Groups

Changing workflows for multiple projects

I have everything in place, and tested, to implement new workflows for all issue types in 6 projects.

Is there any limitation on the number of updates that need to be made when implementing the new workflows?

Also, does anyone know how long changes like this could take?  

1 answer

1 vote
Tessa Tuteleers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 21, 2023

Hi @Linda Redgate , 

If I understand you have 1 new workflow scheme with a few workflows for the different issuetypes that you want to start using in 6 projects? 

You would have to do the following steps: 

  • For each project, go to the project admin and change the workflow scheme to the newly created and tested scheme. 
    Depending on how many issues there are in the project, this could take from 2 seconds to an hour and a half (my personal max with +- 10k issues).
    You will need to map all the statusses that aren't available anymore to new available statusses. 
  • If you need to map statusses (when statusses aren't available anymore), or if you have added new statusses, be aware that you need to check al the following as well
    • Filters for (dash-)boards
    • Column mapping on boards
    • Automation rules

As an admin, there is no limitation of updates, however, you cannot migrate the workflows of 1 project when another project workflow migration is still in progress, so be aware that if the projects contain a lot of issues, you can't migrate them simultaneous. 

Hope this helps!! 

- Tessa

Thanks Tessa

I know how to implement the workflows, so I am good there.

Thanks for answering the timing question -that will help planning the migration.

However, you have answered another question that I was mulling over and I believe that I would need to migrate project by project.  Is that correct?

Tessa Tuteleers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 21, 2023

That's correct @Linda Redgate , 

you would need to go project by project, because the current state of the used workflows might not be the same. For each project you could have different flows for different issue types, so the mapping would not be the same for all the different projects. 
It gives you a little more control of the migration itself.

Happy migration! 

- Tessa 

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events