📣 Feature Update: View Restrictions in Jira Product Discovery

[#1]

You can now sign-up to the Jira Product Discovery Premium plan.

Start your trial here.

Other features of the Premium plan are described here and we've also published an implementation guide.

---

Hi everyone,

We’ve heard from many of you that as more people collaborate in a Jira Product Discovery project, it can get harder to keep views consistent and focused.

Maybe someone tweaks a filter or sort order before a big exec review—sending you into a last-minute scramble to fix what’s broken. Or a stakeholder stumbles across a work-in-progress view, misunderstands what they’re seeing, and starts giving feedback before you’re ready. Or you’re just trying to create a roadmap quietly with a few close collaborators before opening it up to a wider audience.

That’s where View Restrictions comes in—a new feature coming soon to JPD Premium.

It gives you control over who can see or edit specific views, so you can:

• Lock down views for exec reviews and critical meetings

• Collaborate privately during early-stage planning

• Share with the right people, at the right time

Here’s a quick look at how it works:

We hope you’re as excited by this feature as we are and we’d love to hear what you think! Share your thoughts, questions, or ideas in the comments—your feedback will help us shape what’s next.

Cheers,

Amina

[Victoria Aiksa Zapata]

Hello, is this feature exclusive for premium? When is it planned to be release? Tnks.

[Kesha Thill]

hi @Victoria Aiksa Zapata ! view restrictions is exclusive to Premium, which is now available! More info here

[Team Manager]

Hello,
Thanks for the information. It's clear. I'd like to know if all stakeholders need to have a jira account to check projects info. Happens that not all of them are so involved. How can I share info or views with them without forcing an account?
Thank you.

[Peter Quick]

Hi @Amina Bouabdallah ,

We've been patiently waiting for the Stakeholder Role to be introduced. It's not here in Premium, any info on whether it's been dropped from the roadmap?

We need to share a view with people outside our organisation, who won't be Atlassian accounts, and have a Submit Idea capability, as scoped a while back during beta.

Cheers,

PeterQ

[Bill Hoo]

@Amina Bouabdallah Just a kind reminder after a long-term use of View Restriction.

Currently, the View Restriction only applies to the View itself; it does not restrict the filters within it. For example, even if you set up a restricted View, your stakeholders can still reset the filters to see all ideas and all available field values of those ideas—rendering the View Restriction ineffective.

So basically, where is the restriction? From my perspective, this is a broken issue in the current View Restriction feature.

Use Case:

When we say Restriction, we usually mean the restriction to the data (ideas). There are some ideas and fields we don't want stakeholders to see. That is why we restrict a view. e.g., A CEO View, will have bunch of things they would like to see, the cost of the idea, the cost of the development efforts, and the real customer's contact maybe. However, this CEO View should never be seen by other stakeholders. To achieve this, we want to restrict this view to CEO only, while provide another view for stakeholders.

However, currently once the CEO view is restricted, yes, stakeholders cannot see it, this is perfect. But, stakeholders can change their view's filters to see ALL ideas and ALL idea field including customer real contacts... this is a broken behaviour.

Expectation:

View Restriction, should also restricts the Filters and Available Fields. What matters is the idea data itself.

We expect a restricted Filters and Available Fields UX just like how you do with Published Views, but for internal teams usage. Published Views are not suitable for internal use since no Comments, no Rovo AI supported.