The best practice advice seems to be to keep issue screens (etc) simple. Why does JIRA create a new set of all of this stuff for each new project we create? It seems very duplicitous - we don't need a new bug screen, for example, for each project.
Screen Shot 2014-12-01 at 13.06.37.png
I think this idea comes from admins saying they changed a scheme and affected other projects they didn't want to. So the direction JIRA is going is to end up with a set of 7 schemes per project. This will stop admins changing up more than one project inadvertently. But adding a field to 100 projects will now mean editing 100 screen schemes, for example. Not a great trade-off in my opinion, as an admin who will have to clean all this up!
I am pretty certain you are right, but I think it's a poor design. Better a new admin learns that schemes can be associated with multiple projects, maybe from their mistake, than by guiding people to this multi scheme path. Merging schemes is hard once they've diverged, and large numbers of certain schemes types are often at the root of poor performance.
I'm not sure if this feature was added after you asked your question, but now when you choose "Create New Project", you have an option called "Create with Shared Configuration" that lets you select an existing project whose schemes will be used instead.
I just created a project called "<my projectname> Template" and just make all new projects share this configuration.
No more proliferation of schemes. And I just change the scheme in one place for all projects.
There was an update on JIRA and for now a Screen Scheme is created for each new project.
If you want to change the Screen Scheme of a specific project (like setting all projects to the same screen scheme), please follow the steps below:
I understand that these steps will take your time and will make the project creation process longer.
There's a suggestion requesting a fix for this issue. For further information please check https://jira.atlassian.com/browse/JRA-39966, you may vote and comment on it in order to increase its visibility.
Thanks and regards,
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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