I want every user in our company (regardless of group they belong to) to have the same exact fields available to them when they create a new issue. No more, no less. How do I make this happen? Thank you!
Make sure all your issue type screen schemes use the same screen for "create issue"
Remove all plugins that give you any form of field-by-user stuff (Field security plugin for example)
Grant all of your users exactly the same permissions for "Can assign issue to users", "Resolve issue", "Schedule issue", "modify reporter", "set issue security", and the three "attachments" things. (Note that this doesn't mean you have to give them the permission - just the same permission)
Then they'll get identical screens.
Unless they change the defaults on their "fields I want to see" personal settings.
Ah, that's been done by the project template stuff when you click "create project", in an attempt to isolate all the projects. You'll find that if you've always chosen one project type (your screenshot shows repeated use of "scrum" template), they're all using copies of the same screen, so they are pretty much the same, but if you've used different project types, you will probably have to migrate them to use the screens you want to. Because they're all copies though, the question could be down to if you have other adminstrators - if this is a new Jira and you're on your own, then the screens will all be the same unless you've deliberately amended them. If you do have other admins, then ask them, it may be that they haven't changed screens either. That means choosing which "issue type screen scheme" you want to use and then changing each project to use it instead of their own dedicated screens. And think about not using the templates any more.
Ok, we need to go back to the "project template" concept. When you create a project, you select a template, and that template contains instructions for building the schemes that make up a project structure. Sometimes, these schemes are "use existing scheme X" and other times, they are "create new independent scheme with predefined settings detailed in the template code". The Agile template creates new independent schemes, and it's coded into the template. So, if you don't want independent schemes each time, you need to either a) Stop using the Agile template and use another which sets the schemes to shared/default ones b) Use the Agile template, but after using it, change the schemes to the one(s) you actually want to use c) Find/Write a new Agile template that says "reuse shared defaults" instead of "create new" (not available to cloud users)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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