How can you make a Client Role that only can comment on their project but not see all the other user projects?
So far a created a "client role" that has comment only permission, but when I log in as them they still have access to all other user projects. What i'm I doing wrong?
The problem could be in the permission schemes of these other projects. Your client user might be present in a Project Role through membership in the jira-users group for instance, and gain Browse permissions from that. Since any user who wants to log in must be present of that group, your client user is bound to be a member of at least one group.
If that's the case, here's what you should do to fix this with minimal effort:
True. The truly best (longer to implement) solution would be to go and change the permission schemes to use project roles, and project roles so they use a custom group of in-house users, and leave jira-users strictly for login and nothing else. That's how it should have been anyway, external users or not.
And give a crack of the whip to users who share filters and dashboards to jira-users while you're at it. They probably deserve it for something else too, pesky users!
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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