Search blocks by description or jump to a page.
A saved view change bar listing unsaved edits as rows with per row undo, the resulting query, and update, save as new, and discard actions.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
View Changes Bar is the surface a saved view shows once its filters or sort have been edited: a Sprint 24 planning header with a Saved view badge, a change bar counting the unsaved edits with Discard, Save as new view, and Update view actions, and one row per change. Each row names the edit (Added filter, Removed filter, Sort changed), shows the affected token (a removed filter struck through), and carries a per row Undo. A Resulting query line spells out the full query the edits produce.
Changes are one array with an icon, an action label, an optional token, and a removed flag, so an added filter, a struck removed filter, and a prose sort change all render from the same row. The footer notes that updating applies to the twelve people subscribed, which is the fact that makes Save as new view the safer default.
Reach for this block wherever users edit a shared saved view and need to decide between updating it for everyone and forking a copy, wired to your views API so the change list and resulting query reflect the live diff. Per row undo lets them back out a single edit before committing.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the unsaved changes bar on a shared issue view. Other pending edit surfaces:
Tip: state who a shared view affects before the update button; the count of subscribers is what nudges a user toward saving a copy instead.