Save and share views in Jira
Saved views give teams a consistent way to look at work in a space. Space admins can create shared views so everyone starts from the same setup, while individual users can adjust a view for their own work without affecting the rest of the team.
A saved view stores a snapshot of a view’s configuration. It isn't a live link to a saved filter or to another user's personal changes.
What are saved views?
A saved view is a reusable space view that captures how work is displayed in Jira. It can include things like filters, visible columns, grouping, and other view settings, depending on the experience in which the view is used.
Saved views help teams switch between common ways of viewing work, such as:
a planning view for upcoming work
a delivery view focused on in-progress items
a reporting view grouped by owner, status, or another field
Because saved views belong to the space, they help teams work from the same starting point without requiring everyone to recreate the same setup manually.
Create a saved view
If you have space admin permissions, you can create a saved view from the list or timeline in Jira.
Create a saved view from the list
Start in a Jira space and select List from the space navigation.
Use filters and grouping options to refine your list.
Select Configure columns if you want to add or remove columns, then drag and drop to change the order of columns.
Select More actions () for other view options, like hiding Done work items or showing the work item hierarchy in the list.
Select Save or reset view settings (), then select Save list.
Create a saved view from the timeline
Start in a Jira space and select Timeline from the space navigation.
Use filters to adjust the timeline view according to your preferences. Select the View settings icon for additional options.
Select Save view settings () then select Save view.
Who can manage saved views?
Saved views have different capabilities for space admins and regular space members.
Space admins
Space admins control the shared version of a saved view. They can:
create a new saved view
save changes to a view for everyone in the space
rename or reorder a saved view
set a default saved view
delete a saved view
When a space admin saves a view, that configuration becomes the team’s shared version.
Space members
Regular space members can use saved views, but they can’t control the shared version. They can:
open and switch between saved views
change the view for their own use
reset their personal changes back to the admin-saved version
When a regular user makes changes to a view, those changes only affect that user’s experience. They don’t update the shared space view for anyone else.
This table shows a summary of what actions can be performed by space admins compared to regular users:
Action | Space admin | Regular user |
|---|---|---|
Create a saved view | Yes | No |
Save changes for the whole space | Yes | No |
Make personal changes to a view | Yes | Yes |
Reset to the admin-saved version | Yes | Yes |
Rename, reorder, set default, or delete a saved view | Yes | No |
What a saved view includes
A saved view generally stores settings that affect how work is displayed. This can include:
filters applied to the view
visible fields or columns
grouping or hierarchy settings
display preferences
A saved view preserves the context for how results are presented, providing more than just a query.
Saved views compared to saved filters
Saved views and saved filters solve different problems. This table shows a summary of the key differences between these two features:
Feature | Saved view | Saved filter |
|---|---|---|
Purpose | Saves how work is displayed in a space view | Saves a reusable work item query |
Scope | Shared in the space experience | Reusable across supported Jira experiences
|
Includes layout settings | Yes | No |
Can be updated for everyone by regular users | No | No, unless they own or can manage the filter
|
A saved filter focuses on which work items appear. A saved view goes further by capturing how those work items are arranged and shown in context.
How shared and personal changes work
Each saved view has a shared version managed by space admins, and a personal working state for individual users.
This gives teams a balance between consistency and flexibility:
Admins provide a stable default view for the team.
Users can temporarily tailor that view to suit their own work.
Users can select Reset to return to the admin-saved version.
This model helps keep shared views reliable while still letting individuals work in the way that suits them best.
When to use saved views
Use saved views when your team needs different, easy-to-access ways to look at the same space data. For example, a team might use one saved view for weekly planning and another for reviewing daily progress.
Was this helpful?