Under the current cloud hosted version of Jira, we cannot allocate existing workflow schemes to new projects. Creating a new project creates a new workflow each time, which just generates more work to clean this up.
Earlier guides suggested using JIRA classic as an option when creating a project, however this is no longer available. See also:
It's very rare that different projects will have different workflows. Its far more common for projects to share a common custom workflow scheme, which can be maintained across all the projects.
How is this best accomplished?
I also find it helpful to setup a project without any issues as a template for starting from where I know which schemes are going to be shared amongst multiple projects. This allows each project to then have small amounts of customisation without needing to remember which project is the template.
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