Might be easier to explain what is going on from the beginning.
First, think of a JIRA project. It's a collection of issues. It's also where the configuration is hung - so to enable a permission for "I can see issue", you set it in the permission scheme for the project. Now, you've said "I've set only admins and groups can edit issues" but not explained what you mean by "that isn't working". This really is simple - check the permission scheme for "edit". People named there can edit, people not named there can not. That's it.
Now, consider an Agile board. These are easiest to eplain if you think of them as a view. When you look at a board, it has a filter that says "here's the issues to include". The only limitation here is that you must share a board with other users. But that right only lets them see the board. How the use it is a function of the stuff behind the scenes in the project. People with "edit" on issues included in the board will be able to edit them on the board.
Third, we need to look at the workflow. In plain JIRA, that controls who can transition an issue from one status to another. Now, if you go back to the board, your columns are reflecting status. So to enable someone to move a card from one column to another, the user must be able to use the transition in the workflow that goes between the status in the columns
So, to give people "View but not edit"
- Share a board with them
- Make sure they have "Browse" for any projects the board includes
- Make sure they do NOT have "transition" for any projects the board includes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.