Viewers should not be allowed to change the original view filter once the view is restricted.

[Bill Hoo]

Hi there,

One feature request I see valuable to the community, any inputs are welcome.

[Feature Request]
When a View is restricted, provide admins with an option to disallow viewers from changing the View's filter settings. Viewers may add additional filters, but they should not be able to modify or remove the original filter.

[Current Issue]
Currently, viewers can reset a view filter or sorting rule to see all ideas in a JPD project.
This should not be allowed—if a View is restricted, it implies the data in that View is sensitive. Otherwise, there would be no reason to restrict access.

To properly protect sensitive data, the original filter must remain enforced. Just like how it works in Published View.

[Expectation]
1. When a View is restricted, allow admins to choose whether the filter should also be restricted. If yes: Viewers can only see ideas under the original filter. They may add additional filters to refine results but cannot change the original one. If no: The behavior remains as it is today, where viewers can modify the original filter.

2. Once the View is restricted, the Available Fields should be hidden from each idea. Since the main goal to restrict a view is to protect data from internal teams.

Published Views are not a solution here, since they are primarily intended for external users. Internal teams need to be added to the JPD Project and use features like Rovo AI.

In a word, we want something very similar to Published Views, while for our internal team members' usage.

[Use Case]

The product team needs certain ideas hidden from the broader team (sensitive information), i.e., long-term decisions, internal (Product team only) discussions and ideas that are not good to share with other teams.

At the same time, we want to collaborate with other teams tightly (Marketing, Sales, AMs, Devs) within a single JPD project. Our internal team must be added to the single JPD project and use Rovo AI.

That said, we need to maintain data security for both Internal and External teams. Published Page only serves the external teams, we need the same copy for Internal teams.

Thank you all.

[Hermance NDounga · Accepted solution]

Hello Bill, 

Thank you for this suggestion, we've discussed it together and we think it could be a great improvement in the product. 

We will evaluate technical feasability within the next months, and follow back in here for any updates :) 

Best Regards,
Hermance
Sr. Product Manager @ Jira Product Discovery