I wanted to make a user group for read only besides just the subversion control. Is there a quick and easy way to setup a read only user group without having to set the permissions level for each area? Or do you have to setup each area individually for a scheme and apply the scheme?
Given the provided information, you will need to adjust your permission scheme. This should not be that hard since you can just add your read only users to a group, and then add the group to the right permissions. This way, you only need to add and remove people from the group at need. You will not need to adjust the schemes every time your userbase changes.
I created a group called view only. I have also created a permissions scheme called view only. I have added the permissions scheme viewonly to the group view only. Within the view only persmissions scheme I have only given permissions to the group to the following:
View Read-Only Workflow
But the users are still able to comment, edit and all of the normal functionality. How do I make it so they can only view the issues, and not assign anything.
I realize I should have found this earlier. Take a look at: https://confluence.atlassian.com/display/JIRAKB/How+to+make+a+Read-Only+user+through+permissions+and+workflow+conditions
Let me know if you have any questions.
The users are only part of the view only group, with the view only permissions scheme. The only other group they are part of is the jira-users group which I was under the impression they had to be to log in. Do I need to remove the users from the jira-users group? I tried this earlier and the users were unable to log in.
Does the user have membership in any other groups?
Bassicaly the user needs to be a member of Group A and only Group A, Group A needs to have read only permissions in Scheme A, Group A should be a part of the jira-users permission.
I have completed steps 1 & 2. When it gets to step 3 I am a little lost. Steps 3-6 seem to focus on adding more access and I just want to make sure they can read the issues only, not comment or edit the issues. I have tested this with a test account and the users are still able to edit, comment and assign with just the Browse Projects in the View only permissions scheme. I am not sure what I am missing to only allow them to read data.
Under "JIRA Users" the "jira-viewonly" group is now included. They are not included in any other global permissions group.
On my Permission Schemes I have included the "jira-viewonly" group to the "Browse Projects" project permissions only.
The user is able to log in to JIRA but still cannot see the issues I assign them with the following error message.
"You do not have the permissions required to browse any projects.
To change your permissions, please contact your JIRA administrators. "
They can however view the filters.
Glad I could help. Once you have verified that it is working, please mark this as the answer. When other people run into the same issue, this will make it easier for them to find how to solve it.
Also, I highly encourage you to take a look at: http://www.atlassian.com/software/university/overview which is our training program. This will help you get up to speed on how to use and administer JIRA.
It would be helpful if you could provide a little context. What product are you using? JIRA? Confluence? Fisheye / Crucible? Also please let us know what version of the software it is.
Atlassian Support - San Francisco
Enjoyed the support?! Tweet us! #atlassiansupport
Hi guys, I know this is an old issue, but I wanted to confirm:
Do I have to make Workflow changes to create a read-only User Group, or should the changes to Global Permissions (ONLY JIRA Users) and Permission Scheme (ONLY Browse Projects) be sufficient enough to give people read-only access to issues?
Because unfortunately I'm seeing that a user in the new group still has permissions to Comment, Assign and other Actions.
Hey - so I've set up a group that *only* has the following permissions:
Global: JIRA Users
Default Permission Scheme: Browse Projects
For different projects, the Comment button is unavailable. But for some transitions still show up, whereas for others they are not there. So do I need to look inside every workflow and add Permission Conditions all over the place? That sounds... not fun. :-/
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
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