Our instance of JIRA has a lot of projects in it. A lot of our projects share the same issue type scheme, workflows, and workflow schemes. We are trying to keep the number of these items as minimal as possible. Also if we have a company wide process change, we want to apply it to all projects quickly. Therefore, this is the reason we share workflows and etc. Plus we want to keep the system as clean as possible.
The problem is that everytime we create a new project, the new project creates a project specific version of the items I mentioned above. The we manually have to configure the project to use the already in place schemes that our other projects use. While we see benefits to having project specific items, we would rather this be the execption rather the the norm.
I have two questions:
1) Is there a way to disable or modify this "feature" and have new projects default to already in place workflows rather than making their own copies?
2) If not, what is the reasoning behind having the system perform in this manner?
When you create a new project, there are serveral options. For example if I select Simple Issue Tracking then you are correct, a new workflow will be created/associated. In contrast, if you select 'JIRA Classic' as your blueprint style you will not see that behavior.
I was asking similar question some time ago related to project templates. I personally thisnk that it should be possible to quickly create a template with a name a list of the schemes that you want to use for every new project.
Currently I can say that this is not possible OOTB. I would have a solution for you but I see that you are using OnDemand instance, so probably it will be hard to extend your JIRA instance.
If using standalone there is no problem with creating/developing your own Project Template. By following this great tutorial you should be able to easily achieve that:
If this is not a option for you there still is light in the tunnel.. You will need to vote for this ticket and wait until Atlassian will develope some improvements to the core product.
Message in the description is saying that some improvements will be done in upcomming year. Let's hope that this will help in your problem.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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