Manage Issue Layouts and Edit Workflows permissions not working

[Harsh Bharucha]

Even though my account is assigned the right Roles (Administrator, and atlassian-addons-project-access) for the Manage Issue Layouts and Edit Workflows permissions, I am unable to perform those actions. Any ideas on why?

[Harsh Bharucha]

Hi @Trudy Claspill , I'm trying to access the following screen:

Project Settings > Issues > Layout > Edit Issue Layout > Search All Fields. When I try to search for fields and hover over the search box with my mouse, I get a message saying I need the 'Manage Issue Layouts' permission (which I should have with my Administrator, and atlassian-addons-project-access roles).

Thanks in advance for any help!

[Trudy Claspill]

Hello @Harsh Bharucha 

Welcome to the Atlassian community!

What screens are you trying to access to manage the Layout and Workflow?

What happens when you try to access those screens and make changes?

[Trudy Claspill]

Thank you for that additional information.

Can you provide a screen image of the Project Settings / People screen, filtered to find your user record, and expand the Roles drop down to show that it indicates you are a member of the Administrators group?

Can you provide a screen image from the Permissions Scheme associated to this project showing how the Manage Issue Layout permission is allocated?

[Harsh Bharucha]

Hi @Trudy Claspill ,

I've attached the screenshots you requested below:

[Trudy Claspill]

Thank you for the additional information.

Reviewing the image of the Permissions, the Manage Layout permission is allocated only to the add-ons role, not to the Administrator role. The permission needs to be associated to a Role or Group to which you belong, or to you as an individual.

Note also that the "add-ons" role that you are added to says "(migrated)" at the end that is not the same role to which the permission is allocated.

I think you will find that you cannot add yourself to the role that currently has the permission. That role is intended to contain the users that are used by third party apps to ensure those apps have enough permissions to perform the intended functionality. Apps automatically add their user to that role. It is not intended to contain real people.

The same role name with "(migrated)" appender indicates that a transfer of data from another Jira to your Jira occurred. During that process the process needed to bring across that project role, but one with the same name already existed, so "(migrated)" was appended to the name.

[Arturo Oaxaca - Administration]

Hey Tudy. I am facing the same issue. So what is the way to fix it since I only see add-ons migrated as well 

[Trudy Claspill]

Hello @Arturo Oaxaca - Administration 

If your issues is exactly the same as the above and the Manage Layout permission is allocated only to the  atlassian-addons-project-access role, then the Permissions scheme needs to be modified to allocate that permission to another Project Role to which you belong.