We have many projects across JIRA and inside each of those projects we use the basic hierarchy:
- Epic > Task > Sub-Task
We don't use bugs, stories or any other kind of task type. Each of the task types listed above in our hierarchy should have the exact same fields/custom fields in the issue screen.
And if we add new fields, we would want those new fields to be added to all projects.
Basically we want uniformity so that when we create new projects that uniformity is carried over (same issue types, same fields, same workflow, same as much as possible).
We know that there are global contexts and such but they don't seem to work in the way we need. When reading through JIRA documentation it seems so hard to get a straight answer on this and the way JIRA defines things seems very unintuitive (to us).
Is there any straight forward way/guide to achieve this?
Maybe we're missing something obvious so any info or insights would be greatly appreciated!
If you want to lock it down this much, then you can. As an administrator, remove all the issue types other than Epic, Task and Sub-task, define a single set of schemes for projects and only add the custom fields you need, with a global context.
When you create a new project
1) Do not select "next gen" projects
2) Use "share existing configuration"
The problem you're running into is that Jira has lots of options for delegating the power, but it is possible to go around it if you're careful.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events