Does using jira simplified workflow complicate upgrading JIRA

[Lara Ramsay]

Hi there. We have been using JIRA for several years now. We recently started using JIRA Agile as well.

We tried to keep our workflows standard and limited to just a few, corporately, in hoping to keep maintenance at a minimum and provide consistency for our users.

We notice now that if we create new projects using the agile simplified workflows, a new workflow is created for each project.

Should we be concerned that this will cause a problem when it comes time to upgrade JIRA? Is it any more work, is it more time consuming, or are there other things to be concerned about with having (for example) 20 workflows (one for each project) rather than just one workflow shared by projects?

Conversely - is there actually any benefit or time/effort savings gained by now basing all projects on the jira simplified workflow?

Since we've always assumed less is better, we're a bit concerned that we may inadvertently create a maintenance issue, especially when it comes time to upgrade JIRA.

Thanks so much for any advice.

[Nic Brough -Adaptavist- · Accepted solution]

Upgrades - no. 

If anything, it's easier.  Simplified workflows are structurally simple, and won't have any post functions, conditions etc that could complicate it (especially if they're from add-ons)

>Conversely - is there actually any benefit or time/effort savings gained by now basing all projects on the jira simplified workflow

Swings and roundabouts:

• Admins don't have to maintain them, it can be delegated to the board owners.
• You cannot do clever things with them, or enforce process.  All status can go to all other status, no post functions, conditions or validators other than the standard ones apply

[Lara Ramsay]

Thank you!