There are four levels of user in Jira
How they get these rights:
Sounds to me like you need to put your solution builders into project admins permissions. Might make sense to do this with a group and use that group in the permission schemes
As I just said, project administrator is done in the permission scheme for the project. It's not global.
Project Lead is a field that says "this person is the lead on the project". A common thing to do is say (in the project permission scheme, of course) "project lead has project admin rights", but it is optional
The project lead is the project lead, I'm not sure how else to put it.
You name someone as the project lead. They are responsible for the project. You can use that flag in other places so that when a project lead changes (Dave leaves, Bob takes over), you don't have to go through and change it, you just change the project lead. You can use project lead in the automatic assigne stuff, permission schemes and notification schemes, and some other places.
The fact that you let other people administrate the project has nothing to do with project lead, it's a permission to let people admin the project.
I'm not sure why this is so hard. I know there's a lot of it, but I don't know why you keep going back and muddling up permission layers and simple fields.
Each permission is separate.
As I said already, you've got System Admin rights and Jira admin rights. That is controlled by global permissions. You don't want these people to have these rights. So make sure you don't put them in an groups that give them the rights.
Project lead is NOT a permission. It's a field that names a user as the owner of a project. You can use project lead in other places to say "Jira, when you need to send email/use permissions/auto-assign issuess/use workflows, then look up who is currently the project lead and use their account"
In your permission schemes, there is a "project admin" permission. You can include project leads in this if you want, or a specific group, or a role, or other things.
Again, the project admin permission does NOT give the users access to permission or notification schemes. They only get version, component and user maintenance.
Project Lead does not have to be filled at all. If you leave it empty, you can't take advantage of the automatic assignment by component stuff, but it really does not have to be anyone. In a lot of development projects, we actually set it to either the person doing the triage, or the lead developer - not necessarily the project owner, but the person who will be doing the initial allocation of work!
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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