Both a feature suggestion and question in regards to how other orgs handle this issue. One of our power users has pointed out the following:
- Readers cannot use the "Group By" option in view, only sort and filter. Group by is very useful to see things that are relevant for a specific team, person, or time frame. Instead, we have to create multiple copies of the same list view for each of those dimensions.
Summary:
Contributors in JPD cannot access the Group By control on any view type. This is currently locked to Creators and Administrators under the "Manage views" permission. We'd like to request that Group By (and ideally Sort and Filter) be available to Contributors as a personal, non-persistent view option — without allowing them to save or modify the shared view configuration.
Use case:
Contributors in JPD are often stakeholders, engineers, or cross-functional team members who need to navigate and explore ideas independently. The current behavior forces them to consume views exactly as a Creator configured them, with no ability to pivot the data for their own context — for example, grouping a list of ideas by team, status, or strategic theme.
This creates a bottleneck where Creators must pre-build every permutation of a view that stakeholders might need, rather than letting Contributors self-serve within the existing view.
Proposed behavior:
- Contributors can use Group By, Sort, and Filter controls as personal/temporary session state — changes apply only to their own view and are not saved back to the shared view
- Creators and Administrators retain exclusive control over the default/saved view configuration
- This mirrors how filtering works in many Atlassian products (e.g. Jira Software board filters), where users can adjust their personal view without modifying the shared configuration
Why this matters:
- Reduces friction for stakeholder-facing JPD spaces where the majority of users are Contributors
- Aligns with JPD's goal of making discovery work visible across teams without requiring everyone to be a Creator
- The current all-or-nothing model (either full view management or no view controls) doesn't match real-world usage patterns
