Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to restrict which users can view a task board?

Hello. My team and I use our task boards extensively, and are all able to add/edit/move tasks. However, the boss and I would like to have a task board just viewable and editable by us. How do I restrict which users can view our task board?

5 answers

1 accepted

4 votes
Answer accepted

Yes you can do this.

Create a group including the you and your boss. Then create the board. Go to Board -> configure.

Under General , click the edit filter share and change the share access to the group only. Alternately, you can create the filter first and share it the group only and then create the board on the filter. Now only you and your boss can see the secrate board.

But, this will only restrict the access to the board. Some one can still open and view the issues individually. To restrict the complete access create a separate project and your group will have access to this project. This along with earlier solution will allow you to restrict someone to see your tasks.

This still works perfectly in 2021 with a current version of Jira Server.  We use Issue Security to restrict issues in a project to single clients, and restricting the board filters to the client groups definitely did hide the boards from all but the desired client.

Yeah, we got the same problem here, I have two boards for the same proyects, cause those proyects has two components, we want each component having it s own board, but if I want to resctrict the view by groups it only load the "System Groups" not the custom groups that we ve made. Other solution is to create a ROLE for each component and then we can restrict the view.
We want to restrict views by custom groups, not by proyect roles.

Ok, I tried that before, but when I try to share to a particular group, my customs groups doesn t load in the list of groups, it only apperas (Administrators, balsamiq-mockups-editors, developers, users). We have more than 20 customs groups created though...
(Im using OnDemand)

I think this is due to permission scheme. Please check the permission scheme that you have access to. Give the same permission scheme for this group.

Yes, it worked!
The only problem I had was that if I want to restrict by any created custom group, I have to be in that group.
Works Ok now.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you