There's a couple of assumptions in that.
For project administrators, it assumes the permission scheme for that project says "Project admin: role (administrators)" - that is a default, but you may need to check, in case one of your admins has changed it to something else.
Similarly, for system admin, there's an assumption there that the group jiraadministrators is granted the global permission - check that section in admin (the default is for the jira-administrators group, not jiraadministrators)
Same basic concept for Confluence. Confluence has a global permission list, which says "group X can do Y". If you need admin rights, then you need to be added to a group that has them. You can have as many admins as you need (but a standard recommendation is 3-10)
On Cloud, user maintenance is separated from the application admin. You need to ask for user admin rights, not just be a Confluecne admin.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs