nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Assigned to Administrators Group - but cannot delete Issues

JT_0xliz1

NOTE: Some field data has been removed from the images below.

Since assigned to the "administrators" group, how is this possible below ?

I am assigned to the administrators group. The documentation uses the terminology JIRA System Administrators, JIRA Administrators, Administrator, Project Administrator, and Board Administrator - but all in different parts of the documentation. The Settings uses Administrator - which I assume applies to any "Administrator."

So to which group does an "administrators" assigned Group member belong ?

* * * * *

Also, when I follow this:

https://confluence.atlassian.com/adminjiraserver071/managing-project-role-membership-802592468.html#Managingprojectrolemembership-viewing

Choose > Projects.
Choose Users and roles in the left menu to view and manage project role membership.

There is NO "Users and roles" in the web portal.

The only thing in our web portal is "Projects and Project Categories."

* * * * *

Where is a table that lists the different types of "Administrators" and clearly shows the default permissions for each ?

We are looking for WYSIWYG "Administrator" in the classical meaning of an "Administrator."

Does the JIRA System Administrator have to create permission schemes for every single user ?

Accepted answers

All comments

Sam Hall_h1otcf

Hi HJLBX - Roles and groups are different things.

Your user is in the 'administrators' group, but the 'Delete issues' permission is given to the 'Administrators' role. If the 'administrators' group does not hold the 'Adminsitrators' role in the project you are interested in, then people in that group won't be able to delete issues.

Based on your previous queston, I think you are using JIRA Cloud, so I'll refer to the Cloud docs in links below.

To see what JIRA-wide permissions people in the 'administrators' group have, check the global permissions.

(but note that in JIRA Cloud, the 'JIRA System Administrators' global permission is not generally available, becasue it is restricted to Atlassian Tech Support).

To see what project-specific permissions people in the 'administrators' group have, look at the permissions scheme that applies to the project you are interested in. If the scheme grants permissions by project role (as you screen shots show), then you need to check 'Users and Roles' inside the project settings.

One way check 'Users and Roles' in JIRA Cloud:

Select your project from the Projects menu at the top of the screen
Once in your project, click Project Settings (the cog icon) in the left hand nav bar
Then, on the 'Project Settings' page, click Users and Roles.

With the default set-up, you'll probably see something like this:

What this shows is that people in the 'jira-admistrators' group have the 'Administrators' role for this particular project, but people in the 'adminstrators' group do not. Something like this probably explains why your user can't delete issues.

Putting them in the 'jira-adminstrators' group will probably solve the problem for you.

JT_0xliz1

Is there some kind of Reply time-out on this board ? Because if we are working on a reply for a long time, then when we select the "Reply" button, the reply will not post. We have to copy-paste our reply and all formatting is lost. This is getting extremely annoying since it is requiring double-work and extra time that we do not have.

Thanks Sam. We really do appreciate your explanations, but have additional questions. There are also some statements below that hopefully Atlassian Staff will see.

3 of us are sitting here and scratching our heads because in the documentation, it states that Administrators are a Group. See first sentence on this page:

https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html

However, on this page it states that JIRA administrators are project roles (the language can be interpreted various ways):

https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html

The documentation explanations are not clear and getting lucid answers is taking up an atrocious amount of our time - time that we don't have since we are a very busy small team. It is for this very reason that we very quickly dumped Team Services.

The documentation is using vague, inconsistent or otherwise unclear language. For example, only now do we see that a jira-administrator is a Role whereas an administrator is a Group in the above images of the pertinent sections of the web application. From our perspective, the documentation is not WYRIWYG.

Also, we are trying to find in the documentation an explicit explanation of the difference between "Administrators" and "administrators." In the JIRA Cloud documentation, the terminology used is JIRA System Administrator, JIRA Administrator, Project administrator and Board administrator.

Quite frankly, the JIRA Cloud documentation is a convulted mess since what we read does not always exactly correspond to the actual web application.

There is no table that explicitly shows the different Administrators and compares their default permissions ?

If a user is assigned to the "administrators" Group, must they also be assigned a Project role ?

If we assign the "administrators" Group to the Administrator's Role, will this allow the "administrator" to delete ?

So Projects are permssion scheme based (which is exactly what we do NOT want to deal with) with no way to set a base set of permissions for all Projects ?

Sam Hall_h1otcf

Hi HJLBX - Sorry about the slow reply. Missed your response and am busy too! But I'll do my best to help you now.

Firstly, yes - if you spend too much time writing a reply on this board it does seem to 'timeout'. Pretty annoying when coupled with the formatting loss on copy/paste. Both issues have been fed back to Atlassian by several people. Take a look at the feedback forum to see what people are saying and add your feedback in there if you want - it helps make this community better.

Secondly, I agree that the documentation on this is difficult to follow. I'd urge you to feedback to Atlassian on this (in your Cloud instance, click the bullhorn icon in the top menu bar).

Thirdly, I'll try to hep you on the docs and other questions in some further replies below...

Sam Hall_h1otcf

"3 of us are sitting here and scratching our heads because in the documentation, it states that Administrators are a Group. See first sentence on this page:

https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html"

Do you mean this sentance: "Global permissions are system-wide and are granted to groups of users."?

This doesn't mean that the global permissions listed on that page are groups. It's saying that these are permissions that can be assigned to groups. It's up to you to choose which groups you want to give these permissions to.

In the list of global permissions, you'll see that there are two that give you access to the administration functions in JIRA:

1. The JIRA System Administrators permission

2. The JIRA Administrators pemission

Neither of these are groups. They are permissions which you assign to a group (or groups).

A user who is in a group with one of these permissions will be able to see and use:

the JIRA Administration menu (i.e. the cog in the top menu bar) which takes you into the JIRA application admin pages.
an 'Admin' menu when viewing issues which has some useful admin functions
the 'Project settings' page for any project

Take a look at the the Global Permissions in your instance to see which groups have these permissions.

(note that, in Cloud, you probably won't see the JIRA System Administrators one, because it is generally restricted on JIRA Cloud and is only applicable for JIRA Server. I don't know why the Global Permissions help page for Cloud mentions it. I assume because some instances may have it enabled).

By default, I think you'll find people the following groups will have the JIRA Administrators permission:

site-admins
administrators
jira-administrators

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

permission

administration