restricting the access to one single table within one project

[Monika Sobczyk]

Hello,

I am working with Jira Cloud. Is it possible to set different access to tables within one project? How can this be done? 

I got three tables in one project, and would like only one of them to be shared by two different roles. 

I tried to edit the filter share for this table, but for some reason, I can choose only "all roles" in the project without differentiating them. So all the people with access to this project have access to all of the tables, without restriction. 

Is there any other way of making this one table either visible to only a part of the project users or visible and editable outside this project group?

Thank you in advance for your help.

best regards,

MS

[Trudy Claspill · Accepted solution]

Hello @Monika Sobczyk 

Welcome to the community.

Can you clarify what you mean by "table"? Maybe provide a screen image?

There is not an entity in Jira called "table" so I'm not sure what you are trying to restrict.

What type of restrictions are you trying to implement? Are you trying to prevent users from seeing data, or editing data?

[Monika Sobczyk]

Hello,

sorry for being not precise enough.

I mean that I got 3 kanban boards in one project, and 2 groups of users working on it. So I would like the first group to have access to the issues on all of the three kanban boards, and the second group to have access only to the issues placed on one kanban board.

I am tryoing to prevent the second group from seing and editing data placed on two from three boards, and access only one of them. 

[Trudy Claspill]

Hello @Monika Sobczyk 

Boards are just a way to visualize and work with Issues. The Issues are actual "in" Projects.

If you want to prevent users from seeing some issues in a project but not others then you need to implement Issue Security.

Refer to this documentation:

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

You might also want to watch this webinar:

https://university.atlassian.com/student/page/1132603-harness-the-power-of-issue-level-security-in-jira-projects-webinar?sid=002b7036-ca05-43ad-ad62-8c13825e4a90&sid_i=0

...and this training video:

https://university.atlassian.com/student/page/817156-issue-security-in-jira-asb-152-course-description?sid=002b7036-ca05-43ad-ad62-8c13825e4a90&sid_i=1

Another alternative is to put those issues from that third board into a separate project, and don't give the users access to that project.

[Monika Sobczyk]

Hello. many thanks for your help. I will check the documentation you mentioned.

I just thought that maybe there was an easy way to use the different roles in the project for each board, but it does not work that way.

[Trudy Claspill]

You can restrict access to a board based on who you share the board's filter with. But restricting access to only the board is not going to restrict access to the actual issues. The issues could still be found and viewed by using issue search or direct links.

To make issues truly not visible in any way to particular users you have to use Issue Security.