Can't get access to the projects being an admin

[Alex Radevich]

Hi,

In our company, we have a lot of projects in Jira. Recently, I've been assigned to the administrator's team to work with the projects but for some reason, I can't see any project. 

When I'm trying to go through the link to any board, I'm getting this message.

I can't determine what is wrong with the error number. - JEJM7R

If I'm trying to check all projects, I get the info that I don't have permissions but at the same time, I'm an admin.

Please let me know how we can check if we set everything correctly. With other guys everything works correctly.

Best,

Alex R

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You won't be able to do that without tweaking some JIRA code. All you can do is just to leave it empty.

[Borek Bernard]

So if I have a project that jira-developers shouldn't be able to access (and ideally not even see in a list of projects), I just leave the Developers role there but remove any permission this role might have on the Permissions tab?

[Nic Brough -Adaptavist-]

I think there's a misunderstanding here.

You can remove any role you want (although it will stop you removing the Administrators role if it would stop all your adminstrative activity). The same applies to groups.

That's a global action though. If you simply don't want to *use* the role, don't put any users or groups in it.

[Borek Bernard]

Oh I see. So if I want only myself (administrator) on a project, my "People" page will look like this:

Administrators => jira-administrators
Developers => jira-administrators
Users => jira-administrators

Is that correct?

[Nic Brough -Adaptavist-]

Yes, that's spot on.

If your permission scheme is then edited so it doesn't use the "Developers" role, then you can have

Administrators -> jira-administrators

Developers -> [empty]

Users -> jira-administrators

... and that will do the same because the role isn't used. The trick is that the list of roles is a global list that projects can use, but don't actually have to. It's common to see sites quite rapidly add a handful of other roles - Tester, Authoriser, and Read Only are the sort of thing I see crop up most often. Obviously, the tester role is only useful in projects where there's a distinct difference between a developer and a tester, so the dev-only projects ignore it.

[Colin Goudie]

I think you can delete them, because you can certainly add them.

http://YOURURL/secure/project/ViewProjectRoles.jspa

At least, even the default roles have the delete button next to them.

However, I've only ever added them. Never tried deleing the default built in ones.

[Borek Bernard]

In my JIRA 5.0 RC2 installation, there is no Delete button on the People page (not even any action button in the top right corner) so it's basically a read-only table (I can just specify which users and/or groups act as certain project roles).

[Jobin Kuruvilla [Adaptavist]]

The delete option Colin says can be found at the Administration > User dropdown > Roles. Be warned that if you delete it here, the role will be deleted for all the projects. You won't be able to delete it for a single project.