Project Admin vs Jira Admin

[Kimm Michaud]

I'm looking for a comprehensive listing of tasks that project admins can perform on their own projects vs a list of what only JIRA Admins can do.  Can you tell me where to find such a beast?  This would be on JIRA and JIRA Agile.

[Stefan Mueller]

Hello there,
I face the same challenge but also for Confluence.

I'm mostly driven by finding a way to delegate the following to power users

1. Jira:
   1. user group management
   2. create projects
   3. manage all kind of schemes except permission schemes, to avoid that power users gain access to projects which are restricted to them
2. Confluence
   1. manage global templates
   2. manage global blueprints
   3. user group management

It looks like many of the desired delegates are possible reading through the pages listed below. The only thing that isn't possible to have Jira power user, who can create global user groups. The only option is properly only Delegated Group Management in Jira or Group Ambassadors.
Confluence allows to delegate most of the system administrator permission, see Global Permissions Overview and Create and update groups.

1. Global Permission or Group? Clearing up confusion on JIRA Administrators

2. How to see user-group-members as a non-system-admin?

3. JIRA: How to give users permissions to create projects

4. Administering Jira: Configuring permissions

5. Administering Confluence: Manage Users -> Managing Site-Wide Permissions and Groups

6. Administering Confluence: Page Templates

7. Administering Confluence: Blueprints

8. Permission to manage users of a certain group

9. How can I delegate permission for software user to create new project without delegate him jira administrator permission?

10. Need ability to delegate permission to add users to groups

11. Users in the Administrator project Role cannot administer project, only JIRA-Admin group members can

12. confluence spaceblueprint permissions

[Daniel Wester]

There are a some add-ons on the Atlassian Marketplace that will allow you to expand the functionality of the Project Administrator. Deiser's Profields is one (allows you to maintain fields in the project). We have 2: Delegated Administration for JIRA (allows selection of schemes by project administrators and maintenance of permissions and notification schemes) and Project Creator for JIRA (allows you to delegate the creation of projects to non-admin).

There are more so if you're looking at expanding capabilities of the project admins, you might want to look around (some are more enterprise friendly than others). If you're just wanting a list of what can be done right now - I would take  look to through your add ons list as well.

[nidhi bala gupta]

Hi Daniel,

What exactly is the budget of these plugin and which team provide support to this plugin?

Thanks,

Nidhi

[Ramarao Gaggara {Appfire}]

Hi @nidhi bala gupta ,

Please find all the requested details about the plugin Delegated Administration for JIRA at below page.

https://marketplace.atlassian.com/apps/1213035/delegated-project-admin-pro-for-jira?hosting=server&tab=pricing

And you can find the details about the plugin Delegated Project Creator for JIRA at below page.

https://marketplace.atlassian.com/apps/1211157/delegated-project-creator-for-jira?hosting=datacenter&tab=overview

Thanks,

RamaRao

[Lisa Förstberg]

Note that there were some changes to this from Jira SW 7.3 (release Jan 2017) and onwards:

"Project level admins can now modify workflows without relying on global admins to make changes, giving them more control over their own processes while reducing requests on global admins. They can create, edit or delete transitions, or add an existing status to a custom workflow"

In short - Project Admin can modify workflow if it doesn't affect any other project. 

https://www.atlassian.com/blog/jira-software/jira-server-7-3-power-to-the-admins

[Paulo Hennig]

Hello Kimm,

In additional to the others responses, I'd also suggest you to check this other answer  as well.

[Nic Brough -Adaptavist-]

Project admins can maintain the list of versions, components and users in roles in their projects.  With JIRA Agile, they also get the ability to start and end sprints, and maintain boards. That's all they get over a "normal" user.

[Kimm Michaud]

So really, in the Project Admin Summary view, Project Admins can maintain almost anything in the right-hand column but nothing in the left side?  What about notifications?

[Nic Brough -Adaptavist-]

Correct. All the stuff that is handled by "schemes" is a Jira Admin job - permissions, notifications, issue types, screens, fields, and so-on - all Jira admin stuff. I did forget one though - if a Jira admin selects "simplified workflow" for a project, then the project admins may also add/remove status from the workflow (An Agile function, can't do it in plain JIRA)

[Senthilkumar]

Hi @Nic Brough -Adaptavist-  I have a requriemnt.

I have used who is taking care of the Tempo and he should have all access on tempo but he should not have Admin access.

Currently we have provided them with Administrator access and weird part is Site Admin has the same access with Administrator got , except User management.

How can i have that user to access all tempo related stuff, but should not be an Admin.

Need your help

[Nic Brough -Adaptavist-]

You can grant Tempo admin separately to permissions in Jira, but there's only a few things Tempo admins can do - specifically administrate tempo.

[Senthilkumar]

Thanks @Nic Brough -Adaptavist- , is this possible if we can mix some of  Administrator permission and to Tempo Admin permissions.

Basically, i want the user to have all Admin rights only to the project which he is added and Tempo rights for all the projects.

I highly appreciate your help...

[Nic Brough -Adaptavist-]

Yes, you can.  Grant Jira admin to who needs it, and Tempo administrator admin to those who need it too.