nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

can i split the Jira Board and limit the access?

nemsawi

Hi,

we have big project with subteams, and some teams should not see the whole jira Board btw. the Stories and Task of the others teams!

To creat a Jira board for each team will be a never ending story.

Is there something like: spliting the Board for teams?

Thanks and regards

nem.

Accepted answers

Alex Koxaras -Relational-

Hi @nemsawi and welcome to the community,

There is a Jira functionality which is called Issue Security Scheme

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

Setting up a security scheme and creating security levels you will achieve what you ask, without splitting the board or creating new ones. Each team will have visibility of their own issues. Some work needs to be done however.

Let me know if that works for you!

All comments

Alex Koxaras -Relational-

Hi @nemsawi and welcome to the community,

There is a Jira functionality which is called Issue Security Scheme

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

Let me know if that works for you!

Walter Buggenhout

Hi @nemsawi and welcome to the Community!

Getting the fundamentals right is usually not a never ending story. But you do need to consider why certain people should only see certain things:

Is it because they are contractors from an external partner who should not see the work of other (maybe also external) people?
Is it because there is a certain confidentiality to part of the project?
Is it because you want to hide certain parts of the project deliberately from people to increase the chance of failure (as part of the team is missing relevant context)?
...

Just kidding on the last one of course. But as you started by mentioning this is one big project, it is important to determine why you split up work so certain people are not allowed to see part of it. It makes it easier to consider your technical options. Basically you can either:

split the work across multiple Jira projects and set the permissions to the appropriate levels on each project. That is pretty straightforward to do and has the additional benefit that you can still use a single board if you want with data from all projects. People will only see the issues from the projects they have access to.
or stick to your big project and set up issue level security. You don't have to split your projects, but determine separate access levels for each type of user/team. You would have to select the right permission level on each single issue if you choose that approach.

Boards are just a way to visualise issues, so there is no way of applying any access policies on the board itself. It is in the underlying settings that you would need to tweak the access to your issues instead.

Hope this helps!

nemsawi

thank you walter

nemsawi

thank you alex

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud