This is because we have the same issues (plus more) showing in different boards for different groups of people. To limit the confusion I had wanted to make one of the boards read only. However some of those people should be able to edit the same stories on other boards.
I didn't think it was possible without changing a person or projects access, but was worth asking in case I was missing something.
Hi Chetna, if I'm correct permissions on the project determinate if someone can make a change in the issues of the rapid-board.
Make sure that people you don't want to be able to make changes don't have permissions on the workflows and in the issues.
If an issue is read-only for an user, he won't make changes on the board for that issue.
Hope this helps!
I have the same question and my reasoning is following: i'm a product owner and I do not want anyone by mistake changing the priorities of the issues. Classical security rule: everyone needs only essential rights to work on his own tasks. Here it would be: read - yes, modify (i.e., change priorities) - no.
Thanks in advance,
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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