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; } } }

Setting Agile security to limit all project from being seen by all users.

Gregory Hicks

Hey everyone,

I did some searching and wasn't able to find any info on this topic or maybe I wasn't asking the right questions on here...

Anyway, right now we have a shared JIRA environment where multiple projects are using agile. I have corrected the JIRA project issue with groups and permissions schemes so people assigned to project groups can only see projects they are assigned too. Agile from what I can see doesn't have that. When a project lead creates a board, the board is visible to anyone that clicks the "manage boards" tab instead of only seeing the board they need to work on. I have located in the configure option a setting to only allow people from project A to see this board, but I was hoping there was a more centralized way of doing this. I don't want to have to reach out to every project and have them fix this permission.

Any ideas on how to set permissions so that boards are visible only to the people in that project?

IE: Project A should only see Agile board A not Project A able to see Agile board A,B, C, D, E.....

Thanks again!

-Greg

Accepted answers

Philippe Aubin

You got it right. The solution we have here is that all the board are created by admin so we don't have that kind of problem. People still can create board but they must remain private.

All comments

Philippe Aubin

Hi Greg.

The first thing to know is that an agile board ''roles'' are based of the permission on the filter you use to create it. So if you create a board with multiple project and you do not restrict the filter you used to create it, all user from all the project will be able to see the board.

So if you create a board for a team, be sure to create it with a filter you have previously ''restricted'' on the level you need and you should be fine.

Feel free to add on the subject if my answer was not clear enough.

Gregory Hicks

I see what you're say but I am not creating the boards, the Projects leads are creating the boards. What they are doing is "Board from an existing project" and not setting the filter from "everyone" in the configure. I think the only way to resolve this issue is to reach out to each agile board owner and have them edit the "share filter" to the groups I have assigned to the projects. I was just hoping there was a way that I could control this without the need to involve PMs.

Philippe Aubin

You got it right. The solution we have here is that all the board are created by admin so we don't have that kind of problem. People still can create board but they must remain private.

Welcome!

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

Quick Links

Find more posts tagged with

agile

security

issue-security