The saved-view bar appears above the filters once a report has been run.
What a saved view contains
A view stores the whole report, not just the projects:
- Scope: projects, work item keys, saved filter, sprints, extra JQL and the max work items setting.
- Dates: the preset, or the custom from and to dates.
- Refine filters: people, groups, fields, search text, all three NOT filters, transition filters and the bulk-only tick.
- Presentation: activity or table view, which columns are shown, the sort keys (up to five) and grouping.
Reopening a view puts every one of those back. You still press Run to load fresh data, so a view never shows stale history.
Private and shared views
| Visibility | Who can see it | Set by |
|---|---|---|
| Private | Only you | Leave Share with everyone in this Jira unticked |
| Shared | Everyone who can use the app on this site | Tick Share with everyone in this Jira |
A shared view is listed for everyone as Name · shared by <owner>. Sharing a view shares the query, not the data: each person still loads the report under their own Jira permissions, so two people opening the same view can legitimately see different numbers of rows.
Saving and updating
- Press Save view.
- Type a name. Names longer than 120 characters are cut to 120.
- Tick Share with everyone in this Jira if colleagues should see it.
- Press Save.
With a view already selected, the button becomes Update or save as… and you get:
- Update: overwrite the selected view with what is on screen, including the name and the Share with everyone in this Jira tick.
- Save as new: create a separate copy. This is how you duplicate someone else’s view.
- Delete: remove the view straight away. There is no confirmation step.
Who can edit what
| Action | Allowed for |
|---|---|
| Open a private view | Its owner only |
| Open a shared view | Anyone who can use the app |
| Update or delete a view | Its owner. A Jira administrator can also update or delete any shared view |
| Duplicate any view you can open | Anyone, using Save as new |
If you open a colleague’s shared view, Update is disabled and the app says whose view it is and that Save as new makes your own copy. The rule is enforced in the app’s backend, not only in the interface. Private views are never listed for anyone but their owner, administrators included.
Share links
Press Copy share link. The app confirms with Link copied. It opens this exact report, filters and all. The link points at the app’s page on your site and carries the whole query in the ?q= parameter, for example:
https://your-site.atlassian.net/jira/apps/<app-id>/<environment-id>?q=eyJ2IjoxLCJzY29wZ...- Opening it runs the identical report straight away, without a further click.
- The link works even if the saved view it came from is later deleted, because the query travels in the link itself.
- Anyone opening it still sees only the work items Jira lets them see.
- The link always opens the full explorer at Apps → UndoTrail, with the projects the query names.
If your browser blocks the clipboard, the app shows the link on screen so you can copy it by hand.
Posting a report link as a comment
The app sends no email. To put a report in front of someone, post its link as a comment on a work item they watch:
- Press Comment on a work item.
- Type the work item key, for example
OPS-12, and press Post the link…. - The app asks you to confirm, because everyone who can see that work item will see the link and what the report covers. Press Yes, comment on OPS-12.
The comment is posted as you, reads UndoTrail report, followed by a description of the report and the link. Jira’s own notifications then tell the people watching that work item. For a report that arrives on its own every day, week or month, see Scheduled reports.
Copy share link and Comment on a work item appear once the app knows your site’s address, which is almost always straight away.
Reset
Reset clears the selected view and returns to the default report: no filters, last 30 days, 5,000 work items, activity view, newest change first. On a project page it keeps that project selected.
Limitations
- Views are stored per Jira site. They do not move between sites, and there is no import or export of views.
- There are no folders or tags. Use clear names, such as Status changes, payments projects, this month.
- Deleting a view does not warn the people who use it. A share link they already have keeps working.
- A view has one owner. If that person leaves, a Jira administrator can update or delete a shared view, but ownership cannot be transferred, and a private view stays out of everyone else’s reach.
- Views hold the query, never the results. There is no snapshot of a report as it looked on a given day; export the file if you need that.