How can a user view, but not move any issues on an Agile board?

How can a user view, but not move any issues on an Agile board? I tired setting filter shares so only admins and certain groups can view/edit a board and that worked. However I need to set something up where users can view but not edit the board. It seems whenever I try to set this its either everyone can touch and edit the board or they can't see it at all. I also created a permission scheme and set that only admins and certain groups can edit issues and that isn't working.

 

Thanks!

1 answer

1 accepted

2 votes

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

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,314 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot