Can't make new user scheme work

We have migrated from onDemand to on-premisis. We are trying to use active directory to manage users. But the users from the server don't seem to work right.

I have read the instructions here:


All projects use the "Default Permission Scheme."

The DPS uses the standard project Roles: Administrators, Developers, Users

The Administrator, Developer and User roles each contain the user "georgec" – which is a windows account.

But when I log in as "georgec" I can see no projects. When I display my Project Roles, none are defined.

What am I missing?

2 answers

1 accepted

0 votes
Answer accepted

Hi George,

There are a few "usual suspects" for issues like this that you should check -

  1. Make sure that the "Browse Projects" permission in the default permission scheme has some groups or roles assigned to it.
  2. Make sure that your user is a member of one of these groups or roles. You can assign a user to a group or role through the user management section of the admin menus.

If you double-check these but still can't see any projects, there might be something harder to debug involved. You should take this issue to the support team then -

- Simon

Just noticed this note on the "Edit Default Members for Project Role" page:

NOTE: When a new project is created, it will be assigned these 'default members' for the 'Users' project role. Note that 'default members' apply only when a project is created. Changing the 'default members' for a project role will not affect role membership for existing projects.

So I read that as saying if I add a new person or group to a role used in the Default Scheme, it won't get used. That is, in fact, what I am seeing.

Seems kind of short sited.

That message only applies to new projects being created - you can definitely add/remove users from existing schemes assigned to a project.

I agree that you should be able to do that. But here is what I see:

Default Scheme uses roles, for example "user"

I put a new Active Directory group in the "user" role, but the members don't get access to the project.

What I have to do assign the group to each appropriate permission.

Hmm... there may be an issue with the Active Directory Configuration, or the JIRA configuration. It's probably best to go through our support team to get this fixed - I can't think of much else that would cause it without looking at your log files.

Thanks. I have added the LADP roles where needed for each project. We are good to go. No time to dig into this problem. It is now at the if-it-ain't-broke-don't-fix-it stage.

Users must be added to project roles manually. This is due to the fact, that the projectteam is likely to change for different project. Also you can add default members (users or groups) for project roles.

What You are most likely missing is the mapping of users to project roles. to do this go to project administartion, "peoples" tab and ad dthe user "georgec" to any of the roles.

Hope that helps? Cheers, David

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 4 hours ago in United States

Atlassian acquires AgileCraft

         Good Day, Bad bad traffic, not sure why!!!! 1/2 hour commute took me 2 hours today 🤯 What helped me is that I kept browsing LinkedIn until...

25 views 1 0
View post

Atlassian User Groups

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!

Find my local user group

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

Groups near you