i've used a couple of different JIRA deployments over the last few years and one thing i've struggled to understand is why customisations required in one project, or group of projects bleeds through into my own projects.
Whilst i get that inheritance of configuration can be good and may reduce the management overhead by having less configuration to support. If we have a set of projects that are industry specific, health care for example, i don't want to see their terminology in my finance set of projects.
Is there something that describes the relationship of all the different schemas/schema types/screen schemes that would help partition the systems more logically?
thanks in advance for any advice
The basic idea is to define a collection of Jira schemes and use that collection for a set of related Jira projects, i.e. all the health care-related projects. Don't let other Jira admins change those schemes without discussing it with you. Add a description with strong words to those schemes
thanks @Matt Doar [LinkedIn] so is there any guidance / checklists on the schemes that need to be created? I assume that the security model for admins isn't granular enough to allow owners at that level - hence the "strong words"? from browsing the forums i've seen quite a few comments about performance implications of heavy tailoring, is that really a concern? at what point does that kick in?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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