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.
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:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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