Can't access a new project as a user

[Roger Spurzem]

I created a new project called Vendor - InSourceCode - Kimbia. Basically, almost all users except for the KMA/Pursuant Group should be able to access it. I created a new group called Kimbia and only want them to be able to access the new project. I created a custom permission scheme but when I try to access the new project as a member of the Kimbia group I can't get in? I've racked my brain and tried all kinds of things but can't get it to work.

The really strange thing is, when I first set this up about 8 weeks ago, everything worked fine for a couple of weeks and then, all of a sudden, we could no longer access it. I hadn't changed anything. Did Atlassian change something that might have affected this set up?

Please help. Thanks. Roger Spurzem

[Roger Spurzem · Accepted solution]

The group Kimbia has the Browse Projects Permission and Issue Level Security is not configured because I don't need it in this case.

[Nic Brough -Adaptavist-]

Could you list exactly what the "browse" line in the permission scheme for the project says? (Text is fine, just include the whole line of the table)

[Roger Spurzem]

Browse Projects
Ability to browse projects and the issues within them.

[Nic Brough -Adaptavist-]

Well, that explains it - you haven't allowed anyone to browse the project.

[Roger Spurzem]

Everyone can access and browse this new project except for two users. I already have another project where everyone can access it but one user can only access that particular project. That user is not associated with the "Users" group. It has worked fine for over a year now. I want to do the same thing here. I tried adding the two users to the "users" group and, of course, then they can see al the projects. What am I missing? Thanks.

[Roger Spurzem]

Here is some more background:

Using the “blue” user ID and PW, I can’t log into JIRA at all. A month ago, I could. I tried adding the Kimbia group to the “Users” project role for the “Vendor – InSourceCode – Kimbia” project, but that didn’t work.

I want the users Shannon@kimbia.com and “blue” to be able to only access the “Vendor – InSourceCode – Kimbia” project.

I purposely don’t have these two users members of the “Users” group because they can’t have access to all the other projects. I have already successfully done this with the “Pursuant” user for the last year. The “Pursuant” user only has access to the “Vendor – InSourceCode” project, and that is further restricted to only certain tickets.

The puzzling thing is it all worked fine for a couple of weeks and then stopped working. I had not made any administrative changes at all. I find that very disturbing. I notice that you all have been changing the screens, etc. over the last few weeks and making it much harder to find things. I really wonder what else you have changed that might have caused my problem.

[Nic Brough -Adaptavist-]

But the "browse" line you posted has nothing against it. Could you tell us what it actually says?

Also, what do you have under Adminstration -> global permissions for "Jira Adminstrators", "Jira System Administrators" and "Jira users"?

[Roger Spurzem]

The following groups are associate with the Browse line in the permission scheme for the project :

• Project Role (Administrators)
• Project Role (Developers)
• Project Role (Users)
• Group (InSourceCode)
• Group (Kimbia)

Under Adminstration -> global permissions for "Jira Adminstrators", I have the Users/Groups "Administrators" with 9 administrators listed. None of them are "blue" or "Shannon@kimbia.com". Neither of these should have any administrative rights.

I don't have a "Jira System Administrators" category.

Under Adminstration -> global permissions for "Jira users" I have the following Groups:

KMA/Pursuant

Wes Byers

Users

InSourceCode

Should the "Kimbia " Group be here as well? Problem is, I don't want everyone in the Kimbia Group to have access to all projects. The "blue" and "Shannon@kimbia.com" users should only be able to access the one project, "Vendor - InSourceCode - Kimbia".

Thanks for your assistance with this.

[Roger Spurzem]

Do you have any further suggestions? I've run out of ideas.

[Nic Brough -Adaptavist-]

Ok, apologies, I didn't see the first reply.

Your "browse" line looks correct to me because it "group: Kimbia". That means anyone in that group should be able to see all the issues in the project

That is separate from the right to log in. You need to make sure your Kimbia users are also in at least one group in the "Jira users" global permission.

I would not put the Kimbia group straight in there because all new users are automatically added to all groups in the "jira users", so your Kimbia group would suddenly start growing.

My usual advice here is to get rid of the silly default Atlassian give you - they create a users group, put it in "can log in" and then use it everywhere else, making it impossible to lock down Jira in any useful way until you revise the entire scheme. Ideally, you should have one single group for "can log in", and you do not use that group ANYWHERE else, at all, ever, without the reason for use being "this person can use this Jira so they can do this" - I use it in browse-users, bulk edit, and to give people access to the "supporting this Jira project"

To fix your problem in the short term, create a new group called "can log in" or something, put everyone in it (including the Kimbia people), add it to the global "can use jira" permission and then don't use it anywhere else. Then, make sure your Kimbia users are only in that group, and Kimbia, and absolutely no other groups. (Check their roles as well)

[Roger Spurzem]

Thanks. I'll give this a try as soon as I get a chance. Hopefully, later today or tomorrow. Really appreciate your assistance with this. Atlassian has not had any helpful suggestions at all.

[Nic Brough -Adaptavist-]

My suggestion will either fix it, or give us more information on what's going wrong :-) Obviously, I'm hoping for the former...

[Roger Spurzem]

Your short term fix worked. Thank you so much. Atlasssian dodn't have an acceptable answer, but you did. i'm very grateful. Thanks again!

[Immanuel Siagian]

Hi Roger,

Can you confirm whether the group Kimbia does have the Browse Projects Permission, and if the project has Issue Level Security configured, please confirm that Kimbia is a part of it.