Permissions issue (space/project confusion)

Jasmine Guarini - Ext

Hello everyone,

I’m currently setting up a Jira Service Management project and I’m facing a permissions issue that I’d like to clarify.

Context:

• A Jira Service Management project has been created (company-managed).

• I have been added as owner & admin of the service project space (I can access the portal, tickets, space settings).

Issue:
I do not have access to edit the following Jira configuration : 

• Automation rules

• SLAs

• Workflows

• Issue types

• etc 

From what I understand, these settings are managed at the Jira project level, not at the service project space level.

My questions:

1. Is it expected that being space owner & admin does not grant access to Jira project settings?

2. To manage automations, SLAs and workflows, do I specifically need to be added as Project administrator ? If yes, how to do so ? 

3. Are there any other roles or permission schemes that could explain this behavior?

The goal is simply to be able to configure and operate the setup properly, without requesting global Jira admin rights.

Thanks in advance for your help!

Susan Waldrip

Hi @Jasmine Guarini - Ext , welcome to the Community!

To answer your questions:

1. Yes, that is generally expected that Jira Admin permissions are needed for *some* space-level settings, especially if those settings are actually set for all spaces at the global level.

2. You need to be a Jira Admin to change the workflow IF it's shared with another space (this is a separate permission that a Jira Admin can give you to manage your own space workflow if it isn't shared). Space administrators need Administer Projects and Browse Projects permissions to manage space-specific rules (no shared automations). I don't know about SLAs, but you can search the Community and on Google/other search engine and probably find it?

3. You need to have Administration permissions at the Space level, and you need to be in the Users Jira Group (like jira-servicemanagement-users-<your site name>), so check both of those.