Every time a project lead is assigned to a project, she/he needs to be assigned as a project administrator to be able to configure the project and add members.

That seems a redundant step.

Why can't we set up the project lead as a role so that the project lead can be granted permission to administer the project?

I created issue JRA-11011 to improve the documentation.

Thanks Neal.

Thank you Neal,

at the Permission Scheme is exactly the Project Lead-option i have searched. I dont know why i missed this. I have taken over a already running System and this was a point for me i wondered all the time. I will look and test this in the next days, but it sounds great allready.

Maybe it would be good to point at the Documentation of 'Project Lead' in a Project to the 'how to assign Rights to a Project Leader' in the Permission Scheme

/close issue

Here's my explanation of project lead:
Basically - it's the default assignee. Beyond that, it can be referenced in permission schemes by assigning various permissions to the "Project Lead" instead of a particular user. That way, if you ever need to change the lead, all the permissions will automatically follow. For example, johnd is the project lead. And you've granted "Administer Project" and "Delete Issues" permission to project lead. So, user johnd would have those permissions. If johnd is on leave, or changes roles, you can simply change the project lead to user janed, and that user would inherit the permissions to administer the project and delete issues. Doing it this way means the project administrators could potentially grant permissions, as necessary, without needing a jira administrator to edit permission schemes. It's one level of indirectness that allows for flexibility in setting up permission schemes and managing projects.