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; } } }

Site Admin permissions to projects are restricted on Free Plan. Is it by design or bug?

Yevhen Khrapach

I'm Site admin and Jira Admin but seems I don't have ALL permissions in ALL projects.
There is a company-managed project and It is impossible to change the project's permissions or roles on Free Plan. And the Permission helper says "You is not a member of any of these project roles: Administrators, atlassian-addons-project-access" for many permissions on the project. For example, I don't have "Administer Projects" permission. It doesn't take into account that I have "Admin access" to Jira.

That's look like a bug.

What if actual project's admin will be killed? How will I be able to do any administartion in the project?

Accepted answers

All comments

Aaron Pavez _ServiceRocket_

Hi @Yevhen Khrapach

Free plans have several limitations mentioned here:

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

The biggest one is that you cannot modify/add any new permissions.

If you need permissions, you need to jump to a Standard plan.

Regards

Nikola Perisic

Hello @Yevhen Khrapach

Project roles become useful when you add people to a specific role. Users are not available in the free plan.

And also the permissions are not available on the free plan as well. You can subscribe to the free trial of Standard version of Jira, where you will be able to have the permissions and users.

After you are done, you can cancel your subscription.

Trudy P Claspill

Hello @Yevhen Khrapach

As others have noted, with the Free plan you don't have access to customize permissions or add users to Roles. Reference

https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/

Note in that document it says that every user that is granted access to Jira Software gets Administrator access for all the projects. There is no need to grant a user any specific permissions.

So, the question is, exactly how have you been designated a Site Admin and granted access to the Jira Software product.

Atlassian started rolling out changes to user management, so not all Organizations have the same experience. It will be challenging to figure out exactly what is happening with your site without screen images.

Let's start with this. Are you able to access https://admin.atlassian.com? If so, so you get prompted to select an Organization? That will happen only if you have access to more than one Organization.

Assuming you do have access to the admin hub, what options do you see?

Can you select Directory and select Users?

Can you find your own user account and display the details for it?

Yevhen Khrapach

Your answer looks strange to me.
Project Roles exist and Users exist and Permissions in all plans. Free plan has only limitations on their management.
If users and permissions are unavailable Then how do I not have PERMISSION and another USER has it (thats that Jira UI says to me)?
About temporary subscription that you propose. I don't need some special permission on a special Issue. I just need general permissions (unlimited) as Site/Jira admin. Do you think it shouldn't be allowe in Free Plan?

Yevhen Khrapach

I don't need some specific permission on specific Issue what Standard plan is about. I don't want to configure permissions at all.

I just want as Site/Jirs Admin to do any possible modifications that another users may do on my site. For me it looks logical to give Admin all permissions if Role/Permissions model is simplified on Free plan.

It was Permission/Role management available on Free Plan some time ago as I remember. Another user was set as a Project Admin and he is able to delete Issue in the project. I don't know was I able to delete issue or not before the limitations introducing but I was able to add myself to Project Admin role. And now I can revoke access to site (same like deletion) for user that can delete an issue but I can't delete an Issue myself and can't set any other User to be able to delete an Issue. This means that not only Permissions, roles, and issue-level security are limited but basic functionality is limited. And that's looks like a bug.

Trudy P Claspill

I was reviewing your post again an I noticed you said this:

And the Permission helper says "You is not a member of any of these project roles: Administrators, atlassian-addons-project-access" for many permissions on the project.

The default permission scheme for Company Managed projects in Jira sets all permission to be available to

Project Role
- atlassian-addons-project-access
Any logged in user

The message indicates that somebody has changed the permissions scheme so that it is instead

Project Role
- Administrators
- atlassian-addons-project-access

This would be a problem.

It is, indeed even in the free plan, possible to create a permission scheme like that, and then associate that permission scheme to Company Managed projects. I've done that as an experiment.

When that occurs, a user would have to be explicitly added to the Administrators role in the project to have the permissions. But in a Free plan users are not explicitly assigned to any roles. So the impact is that the user loses access to the permissions in that project. To ensure that all users have permissions in the projects, the Any logged in user option has to be set for all the permissions. Wherever that is missing in the Permission Scheme for Company Managed projects in a Free plan, all users will not have that permission in that project.

So, for a project where you are having this problem, let us start by confirming what type of project it is. Please go to the Projects menu and select the View all projects page and find the project in the list. Tell us what it says in the Type column.

Next we need to look at the permissions for the project. If you are a full Jira Admin, go to the gear icon and select Issues. Then select Permission Schemes. Find the name of the project in the Projects column. Click the Permissions link on the left near that to display the Permission Scheme details for that project.

If you don't find the project name on the above page, that could mean it is a Team Managed project instead, which will require different steps to diagnose.

When you have the Permission Scheme for the project displayed, grab a screen image particularly for the Administer Projects permission. Share that screen image with us.

Yevhen Khrapach

You say "Note in that document it says that every user that is granted access to Jira Software gets Administrator access for all the projects. There is no need to grant a user any specific permissions." But that doesn't work in fact. Because I DO NOT HAVE access to all Jira functionality for the specific project that was created years ago.

>how have you been designated a Site Admin and granted access to the Jira Software product.
I created the site and organization on Attlassian at 2017. So I'm "organization administrator" and "Site administrator".