Jira Read Only permission

[Deepak]

Is there any workaround to create or provide read only Jira admin permission?

Thanks

[Radek Dostál · Accepted solution]

Jira Administrators come in their full glory and there isn't any framework to support read-only access so I don't think that any workarounds are possible - you would need a new global permission, web condition, implement that web condition on page templates, implement filters on REST endpoints (and specific ones at that). There simply isn't any good foundation to do this and any efforts at it would be (in my opinion) futile, because you'd have to basically modify the source files so much that you'd end up creating a new tool at some point due to the differences.

Are there any specific resources they need to access? What comes to mind is creating a plugin providing new pages (on your own terms and conditions who can access those, e.g. based on group?) with the information they need. So you wouldn't make them a full admin, just expose extra information for them.

[Larry Dillard]

We'd like to provide just "get" Jira admin api functions to some users so they can list users and groups but not update users or groups on all projects.

I've been told that there might be a way to do so by creating oauth credentials with read only access, it may or may not need to include a new app creation.  

[Sachin Dhamale · Accepted solution]

@Deepak - What do you mean by read only?

We can restrict the only following task from Jira admin nothing else

Here is a list of administration tasks that only Jira System Administrators (not Jira Administrators) can perform:

• View or manage tasks from the the Systems menu.
• Configure Jira's SMTP mail server for notifications (but they can configure POP/IMAP mail servers for the receipt of email messages that create issue comments and new issues, and fully administer email notification schemes).
• Configure a CVS source code repository (but they can associate a project with a configured repository).
• Configure listeners.
• Configure services (except for POP/IMAP services).
• Configure issue cloning.
• Change the index path (but they can reindex and optimize the index).
• Run the integrity checker.
• Access logging and profiling information.
• Access the scheduler.
• Export/backup Jira data to XML.
• Import/restore Jira data from XML.
• Import XML workflows into Jira.
• Configure attachments (note that Jira Administrators can set the size limits of attachments, enable thumbnails, and enable ZIP support).
• Add gadgets to the gadget directory.
• Configure user directories (e.g. LDAP).
• Configure Application Links that use an authentication type other than OAuth.
• View user sessions.
• Access license details.
• Grant/revoke the Jira System Administrators global permission.
• Edit (or Bulk Edit) groups that have the Jira System Administrators global permission.
• Edit, change the password of or delete a user who has the Jira System Administrators global permission.
• Upload and/or install an app.

Accept the answer if it helps

[Deepak]

@Sachin Dhamale  Thanks for the update. Read Only - To provide read only Jira admin access to some of the project managers.

[Sachin Dhamale]

@Deepak  In jira There is no read only term for jira admin. Either user has jira admin access or not. can you please tell us what is the your use case?

[Sara Lam]

@Sachin Dhamale , in my organization, only one small group has jira admin access to PROD Jira instance.  I'm a jira project developer who develop new or improve certain existing jira projects in DEV Jira.  Each time, when jira admin implemented something new in PROD Jira, my users would show me some errors but I have no way to view the settings in workflows, automation and custom fields.  If I had the Read Only admin access in my projects, it would be much easier to trouble shoot those errors so that I can make change request to Jira admins.