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

Tech Support

Yamin ZAKARIA

We have brought the premium licenses, the support directs you to a FAQ/AI page for your solution. That is no helping at the moment.

I have lost the ability to create workspace (Project) and I have tried to use Rovo but the set of steps produced by that does not match what is available in the Cloud Jira JSM software.

I am org admin and member of all the admin groups.

Can I get some urgent assistance please ?

Regards

Yamin

Accepted answers

All comments

Matthew Sinclair

Are you a Jira App "Admin" ?

That will open up the Jira-Admin control panel. (sounds weird but I seem to recall something to that effect on the Exam)

Check your org admin control panel and make sure you have that on your account.

It's not billable as far as I know.

Arkadiusz Wroblewski

Hi @Yamin ZAKARIA

Organization admin access doesn't automatically grant the Administer Jira permission. I'd recommend checking Jira settings → System → Global permissions.
As a Premium customer, you can contact Atlassian Support here:
https://support.atlassian.com/contact/
Regarding space creation, is the option missing, or do you receive an error?

Please remember we are here Community members and not Atlassian Support

best,

Arek🤠🧙‍♂️

Sami Shaik

@Yamin ZAKARIA ,

@Arkadiusz Wroblewski has the cause: organisation admin is an Atlassian Administration role, and creating a space is a Jira permission. The two are granted in different places, and “member of all the admin groups” can still leave the Jira one missing. Two checks, in this order.

1. Are you an App admin for Jira on this site? In Atlassian Administration (admin.atlassian.com), Directory, Users, open your own user. In the roles column for Jira Administration (the Jira apps share one admin console, so the role is granted under that name) you should see App admin. If it shows User, select Grant access and set the role to App admin. Atlassian’s page is explicit that an app admin is a separate role from an organisation admin: “An app admin can manage settings for a specific app”, and an org admin does not get it automatically. If your organisation has more than one site, check that you are looking at the site where the space should be created; org admin spans the org, app admin is per site.

2. Does your group actually hold Administer Jira? In Jira, Settings, System, Global permissions. Atlassian’s page states that Administer Jira is what lets users “create new spaces (both company-managed and team-managed)”; the separate Create team-managed spaces permission covers team-managed only. Find the row for Administer Jira and confirm one of your groups is listed. “All the admin groups” sometimes means the organisation’s admin groups and not the jira-admins-<site> style group that this row points at.

If step 1 shows App admin and step 2 shows your group, and the Create button is still missing, that is the point to raise with Support as a Premium customer, with both screenshots attached, because the permission model says you should have it.

References:

Yamin ZAKARIA

Thanks for the response -

This https://support.atlassian.com/contact/ led to FAQ or submit your question to an AI bot. Neither are helpful here.

I need to speak to a human

Yamin ZAKARIA

Hi

I have the option to create space and I did create 3/4 spaces earlier but now I get the following error -

//
Space not created

For some reason the magic didn't happen. Click Create to try again.Contact support

Yamin ZAKARIA

Hi Sami

I have the App admin role. But it seems I was removed some how from the Administrator Jira group. I have added myself back and now I can create the spaces.

Many thanks for your swift response.

Regards

Yamin

Sami Shaik

Glad it is sorted, @Yamin ZAKARIA, and thanks for closing the loop. For anyone landing here later: the App admin role alone did not give him Create; membership of the jira-admins-<site> group (the group holding Administer Jira under Global permissions) did. Worth a look at the Atlassian Administration audit log to see who removed the membership and when, so it does not silently happen again. If the answer helped, marking it accepted helps the next admin find it.