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

Can't access a project even when I'm admin

ranido

I've just start to use JIRA today. I've import issues from BitBucket project I had.

I invite team members and everything was fine.

Now, I've login into our on-demand site and even though I'm in the administrators group I can't see the project. The funny thing is that if I go into JIRA Administration -> Projects I can see and change the project settings but not access it.

I've created a new test project and for that test project I can access without a problem.

Can someone explain to me where did I go wrong?

Thank you,

Ido.

Accepted answers

Nic Brough -Adaptavist-

That's the most likely explanation - your access schemes must say "browse: role of users"

By the way, "Admin can see/do everything" is a dreadful access model and it's one Atlassian have not made the mistake of falling into. Admin gives you admin rights, not access to anything else. With admin rights, you can investigate and change the other rights, add yourself as necessary, but admin is just for admin.

All comments

Elisa [Atlassian]

Hi Ido,

Did you check if the admin user has permission to access it. Sometimes you can configure but not access it. Permissions can be tricky sometimes.

ranido

You are right the permissions can be tricky.

I'm looking now at the project config, inside Roles settings and I see my user both as the Project Lead and and in Administrators and Developers project roles.

I think that should be enough, right?

ranido

I've add myself to the Users Project Role and now it looks like I'm able to both see and administer the project. Is it possible that because I was not in the Users Project Role I couldn't see the project?

Elisa [Atlassian]

Hi, good you found the way with the permissions.

Yeah, it is possible not to see something because of the roles 'cause they work like restrictions.

Hope I could help!

Cheers!

Nic Brough -Adaptavist-

That's the most likely explanation - your access schemes must say "browse: role of users"

ranido

I see, thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-cloud

jira-administration