I want to add new users to my jira boars, but when I do the users don't see the project i'm trying to give them acces to. There seems to be a problem with the project, because when I make new projects an user sees the new project and the sapce, and when I give this user admin rights, he'll see the space, but not the project.
How can I assign this user to that project?
Check the permission scheme and roles as a combination. In addition there is a separate permission for the app istelf
Hi @Luuk Post
What do you mean, the term project in Jira has been replaced by Space.
What type of space are you using team or company managed, have you added to use to the access or people section on the space and granted them a role.
In Atlassian Administration have you granted the user(s) access to Jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, i've given the user acces to the space, I think. The space seems to be company managed, but as i'm the company owner, I should be able to manage this space then.
When I try to acces the jira-borad it isn't there and when I try to filter on the list I get this problem:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Luuk Post
The JQL tell you that there is not space with space key CK.
So this means the user is not assigned a role on the space or there is no space with space key CK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes that's the problem. I can't seem to find how to assign this user to the space and thus to the board. Because every other user does have this project in their JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Luuk Post
This role is from Bitbucket to see Jira issues.
This users can't be added in a Jira space role, as this is not a user that can be granted permissions on a space directly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Luuk Post
Can you show screenshots of the users in the space, and of the users profile in admin.atlassian.com?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This user is not listed in the space settings under people. But When I try to add this user, I get a message:
"On a free plan, you can only add people using your site's administration settings. Upgrade your plan to better control who can access this space."
And in admin.atlassian.com (what I think is the site's administration setting) i can't see the method to add the user to the space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mean this? Because when I click the contentkalender project role link, then I get refered back to the space settings --> people and there I can't add people to the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would separate this into three checks, because Jira access can fail at more than one layer:
1. Product access: confirm the user has access to Jira in admin.atlassian.com.
2. Space/project role: confirm the user is actually in the role used by the space/project.
3. Permission scheme: confirm that role has Browse projects for the relevant project.
If the user is really an automation or pipeline-style account, I would also document that separately from normal human users. Those accounts often become confusing later because they look like users, but the owner, purpose, and cleanup rules are different.
The main thing is to avoid checking only one layer and assuming the access story is complete. Product access, role membership, and permission scheme behavior all need to line up.
The risk is fixing the visible board problem while leaving the real access path unclear. That is what makes later cleanup hard: the account exists, the permission seems to work, but nobody can explain which layer is actually responsible or whether it is safe to remove later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the help.
1. The user has acces to JIRA and can see the other projects
2. The user is assigned to this project, I think. but there is no way to really check as the normal way to check this is not visible for us as we are in a free space.
3. The user doesn't have the browse projects permission, used by the space project, but here I come in some sort of loop, where I can't assign roles to this user as we are in a free project. But in order to see the project, the user should have the browse projects permission. I even made the admin, but that doesn't give them these permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Luuk Post
You need to check the Browse projects permission and if that user is part of the role within that permission. Best practice is to assign roles to the users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can check this if you are project administrator and if you see the Space settings when you click on three dots in left sidebar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This user doesn't have this permission.
Where can I assign this permission to this user? Beacuse in the space settings - people I can't change this, but in the user management I also can't change this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to go to the space settings -> Permissions. Locate Browse Projects permission, edit the permission scheme and add the individual user Bitbucket Pipelines.
CAUTION: Changing the permission scheme if it's a default one, may apply to other projects sharing the permission scheme. First check with how many spaces your permission scheme is shared with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, when I do this, I get an error: 'permissions aren't editable on the current plan', so I can't seem to assign this to that specific user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is the issue. You are on free plan, which doesn't have permissions. Permissions are available in Standard plan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.