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

Limiting Visibility to Seeing Risks in Jira Roadmap Tasks and Risk Register - JIra Server not Cloud

tim comella

Hi, All,

I am supporting Jira in Federal space but this probably applies to all industries, We have a need to create the equivalent of WBS Issues (child Tasks) under parent Features in Jira, including marking some as Risks under the Feature. So far so good, this works fine. And when a Risk is added it shows up correctly in our Risk Register.

Question is this: would like to limit who can see the Risks in the Plan (Roadmap). Some entered risks may be sensitive - budgetary risks, resourcing risks etc. Want to limit which users have visibility to seeing the risks.

This is for Jira Server environment - not Data Center and not Cloud.

What is the best approach to limiting this visibility. Thanks!

Comments

Craig Schwarze _ProjectBalm_

Hi Tim,

Are you using a tool to track your risk register? If so, which one?

kind regards<
Craig

tim comella

Hi Craig,

I am aware of some add on tools however we are simply using the built in capabilities of Jira Server. When viewing an Issue declared as a Risk, there is a hyperlink in that detail screen that, when clicked, navigates to risk register. Also have some built in risk matrix Gadgets that can be added to a dashboard. I do not believe those are custom or 3rd party.

Jonathan Muse {Appfire}

Assuming I understand correctly there could be several ways to accomplish this. It may be as simple as adding an issue security scheme to your project. If not, there are add-one like Power Scripts (and others) that could hide the risk based in user group membership or or some other config like that. Or, if you have the skills you may be able to accomplish this using JavaScript inside the announcement banner.

I would try to accomplish your goal in that order:

Issue security scheme
Power scripts (if you want to do this yourself)
script runner (if you want to pay someone to solve this for you)
javaScript (if you have the skills)

tim comella

Thank you, we will try these, in particular the Issue Security approach #1.

tim comella

Looks like Cloud version of Jira has more capabilities in Issue level restrictions/policies. Our environment is Server.

Welcome!

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