need to assign permissions to edit screens but limit it to a specific project

[Randall Okon]

we have a project with several sub/custom screens and workflow. I need to give a user the ability to edit the custom screens add/change fields etc. but do not want to add  the global admin role. 

He is a project lead, and has extended admin for the project. the "screens" menu doesn't display and he cannot edit the components he needs to.

[Trudy Claspill · Accepted solution]

Hello @Randall Okon 

Welcome to the Atlassian community!

You have tagged your post as being for Jira Cloud, however per this issue  the "extended project admin" option is not available in Jira Cloud. Are you sure you are using Jira Cloud? If so, can you show us how the user has been granted the extended project admin permission?

What exactly is the user accessing when trying to find the option to edit screens?

[Randall Okon]

We are moving to the cloud instance soon. We currently are on-prem
Ie extended--PA is going away, in either case, how do I or can I give the edit permissions only  to the project and the sub task custom pages?

They do not appear in the left side menu unless a person has global admin!

[Trudy Claspill]

There is an open change request asking for the Extended Project Admin option to be added to Jira Cloud.

https://jira.atlassian.com/browse/JRACLOUD-70190

Otherwise in Jira Cloud there is not an equivalent option to allow non-Jira Admins permissions to make such modifications for Company Managed projects.

Jira Cloud has a concept called Team Managed projects which allows the Project Admin to control all customizations associated with the project. But that comes with other differences in project and board functionality and challenges. One challenge is that none of the customizations can be shared with other projects, so you are not able to enforce any standardization across Team Managed projects. You should do an in depth exploration of Team Managed projects before deciding if you want to give that option to your teams. Also, migrating between Company Managed projects (which operate the same as projects on Jira Server/DC) and Team Managed projects has limitations that would need to be considered.

[Randall Okon]

The extended admin role does not give this individual the access to modify custom screens created in support of one project, which is more of a "function". The project is a process with custom screens, fields and workflow. He can see and edit workflow but not the custom screens. With no solution it appears we will need to give in and make him a global admin and accept the risk.

[Trudy Claspill]

I don't have a Server/DC instance to test against, but according to the training I took from Atlassian University a user with Extended Project Admin permissions in a project can edited the associated screens to

- remove fields or add existing system and custom fields

- change the order of fields

when

- the screen is not used by any other project

- the screen is not a Transition screen

- the screen is not a system default screen.

That information was in the ACP-610 Managing Jira Projects for Data Center and Server course.