Project admin unable to create components

[Juliette Bramall]

We have two users with the role Administrator in a company managed project  (i.e. they both have the same role(s)). One is able to create/edit/delete components, but the other is not. Note, the one who can create/edit/delete components is the project lead. Reading the documentation here https://support.atlassian.com/jira-software-cloud/docs/configure-jira-components/ both should be able to create/edit/delete components.

Thanks in advance. 

[Juliette Bramall · Accepted solution]

The issue was with the user's account. She had been added to the project using her email address, rather than adding her Jira account. As soon as we added her correct user profile, she was able to create/edit components. 

[Staffan Redelius]

Thank's @Juliette Bramall for the clarification. So the users had two accounts in Atlassian and was added to the project with the "wrong" account?

[Juliette Bramall]

Not quite. The user only had one Atlassian account, but her email address had been added as a project admin, rather than adding the user. If that makes sense. 

[Juliette Bramall]

Going into the user admin area there is only user with that name. 

[Staffan Redelius]

Ok, I understand. It looks like the user in red is a Jira-Service Management-Customer. They are users that have access to the Customer portal but normally no access to Jira. 

You can check that under Administrator ->Groups and see if you find her in the "Jira-Service Management-Customer" group

[Staffan Redelius]

Hi @Juliette Bramall 

To be able to manage components you need to be a Project administrator (or a Jira System administrator)

If you go to Project settings -> People are both users Administrators? Or is the role Administrator set to a group? In that case are both users members of the same group?

In the picture below I am personally added to the role "Administrator" (which is the Project administrator for the project) All users who are member of a specific group in this case "jira-administrators" are also Project administrators in this specific project based on their group membership. 

Let me know if this is of any help!

Best regards,
/Staffan

[Juliette Bramall]

Hi Staffan

Many thanks for your response :)

Both already have the Administrator role like in your screenshot. 

Best regards
Juliette 

[Staffan Redelius]

Ok, that IS strange.

Can you check with "Permission helper" (top right corner) under Project settings -> Permissions 

1. Choose the user that can't manage component and any issue in the project 
2. Choose Permission "Administer projects"

You should get a clue on what permissions are missing.

[arielei]

Hello @Juliette Bramall 

You problem is probably with the permission scheme.

Check if your permission scheme is set for project roles or single user or group.

the best approach is to use project roles.

[Robert Wen_Cprime_]

Totally this.  To be specific, you want to ensure that both your users have the Project Admin role and the role is allowed the Administer Projects permission in the permissions scheme.

Some documentation is available here: https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/

[Juliette Bramall]

Hello Arielei
The permission scheme is set for project role. I don't understand why one user can create components, the other cannot. Yet both have the same permissions. 

[arielei]

Hello @Juliette Bramall 

Then i suggest you will do the following:
1. click the cog wheel in the upper right corner and select System

2. in the left menu, scroll down to Admin Helper and select Permission Helper

3. Check the user

[Prachi Bolar]

Hello,

Welcome to community :) 

if the users have the right permisison, that is the Adminstrator role then they should be able to edit delete the component 

Could you please check if the affected users is logging in with the right email or so? 

Thank You,

Prachi

[Juliette Bramall]

I've raised a support issue with Atlassian and will document their response. 

[John Funk]

Great - looking forward to hearing that haha.

[Juliette Bramall]

I've worked it out. It's seems that only the project lead that can create/edit/delete components. Which isn't what the documentation says https://support.atlassian.com/jira-software-cloud/docs/configure-jira-components/

[John Funk]

@Juliette Bramall  - That most definitely should not be the case. You should report that to Atlassian for them to investigate. 

https://support.atlassian.com/contact/#/

[Alexander Hohmann]

What type of administrators are your users? In company-managed projects, only Jira Admins can create components.

[Juliette Bramall]

Hi Alexander

They both have the role of Administrator in the project. And the permission scheme for the project give the Administrators the ability to administer projects.

Thanks
Juliette 

[Alexander Hohmann]

@Juliette Bramall As far as I know, a Project Admin can configure components, but to create them, you need a Product Admin, in this case a Jira Admin, if components are to be used in a company-managed project. I suppose that is meant to standardise for reusability and keep the total list of components short.

[Staffan Redelius]

But that doesn't make sense to me since components only live within one project (compared to labels that are shared within the instance).

If you have the role of Project administrator you should have the permission to create/update/delete components if the Permission schema allows the role to "Administer project". Regardless if you are project lead or not.

@Juliette Bramall please update the thread if you get an answer from Atlassian.  I wasn't aware of this and can't remember seeing it in any documentation.

[Alexander Hohmann]

Indeed, you are right. I got this wrong. Contrary to labels, components exist only in the project in which they have been defined.