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

Restrict Hierarchy in Share

Chris Steenwyk

I was wondering if there was a way to restrict what levels of the hierarchy are visible when sharing a link the my plan.

For example, if I want to share my plan with a program manager and want to allow them to see my features but not my individual tasks. Is that possible? If so, what is the best approach?

Comments

Joseph Chung Yin

@Chris Steenwyk -

You should be able to implement "Issue Security" setup to restrict visibility to issue access in your Jira project. AR plan will honor this setup since it pulls issues from your Jira project(s).

Hope this help.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Dave

Hi @Chris Steenwyk ,

One option here might be to have a separate plan with issue sources that don't include the task level issues. You'd need to do this by building custom JQL filters that eliminate the levels you're not interested in.

This means that when you share that version of the plan it won't be possible to see those lower level issues. The limitation of this approach is that you'd no longer be able to rely on "roll-up" data from those lower level issues (i.e. if the dates of your epics were derived from their descendants rather than being explicitly set as attribute values).

I hope that makes sense - let me know if not!

Regards,
Dave

Welcome!

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

Quick Links

Find more posts tagged with

server

advanced-roadmaps