[Feature Request] Ability to save Named Snapshots that do not get auto-deleted.

[Kelendral-gh]

trafficstars

I would like the ability to Create Named Snapshots that do not get auto-deleted. Currently pressing the Create Snapshot button just adds another snapshot to the list which will be pruned when the criteria for pruning is met. This does not meet the need of being able to return to the subject matter at a later time. It would be great to be able to Create Named Snapshot, then get a prompt for a name (ex. Programming) which could be returned to at a later time without fear of it having been deleted.

[Dook1]

I vote for it.

[prmichaelsen]

Different sections in snapshot viewer for manual snapshots versus automatic snapshots #161

[prmichaelsen]

Ability to rename snapshots #317

[prmichaelsen]

named snapshots (or panels) with selection menu #993

[prmichaelsen]

I have some preferences on how such a feature would work and would like to contribute them to this thread.

Acceptance Criteria

1. User can create named snapshots, known as "User Snapshots"
2. "Create snapshot" navigation bar element creates User Snapshot by default
3. When clicked, "Create snapshot" navigation bar element opens dialog to name and save User Snapshot
4. Ctrl + S hotkey opens dialog to name and save User Snapshot
5. Ctrl + O hotkey opens list of User Snapshots so user may select one to open
6. User Snapshots are not automatically pruned
7. Auto snapshots are still pruned, if configured
8. User Snapshot save directory is configurable

Use Cases by Acceptance Criteria

• Acceptance Criteria 1 - Allows me to organize my snapshots logically instead of temporally. Currently, my best snapshot organization method is to export the snapshot, name the file itself, and import it again when I am ready to use it.
• Acceptance Criteria 2 - Allows me to store User Snapshots to my company's approved file cloud sync solution. By managing snapshots statically in plain text in the directory of my preference, I now have the ability to implement other potential workflows. For instance, I could commit my snapshots to a git repository to version them or share them with colleagues.

User Stories

User Story 1

As a Sidebery user, I need workspaces with different panel configurations to manage different work contexts because managing panels and windows for several different contexts becomes disorganized and cluttered. User Snapshots would allow me to manage these different contexts effectively, reduce context and panel overlaps, and reduce the total number of panels needed.

User Story Details

I have different contexts for different projects or categories of work that I am doing. Currently, I use panels to manage this. However, this solution is not always ideal.

• I find panels limited when two projects utilize the same "category" of panel. For instance, an "AWS Docs" panel for "Project 1" and "Project 2". I can create a panel for each context, e.g. "Project 1 AWS Docs" and "Project 2 AWS Docs" but this becomes cluttered the more panel categories I need.
• I could use one "AWS Docs" panel with a "Project 1" Window and a "Project 2" Window, but this becomes cluttered the more projects I need to work on.
• Different types of work require different panel configurations. "Project 1" may use "AWS Docs", "AWS Console", "Stackoverflow" while "Project 3" may use "GCP Docs", "Tensorflow", "Python Docs", "GCP Console", "Stackoverflow", and "Jupyter"

---

@mbnuqw, is there any update on the status of this feature or is it already on the roadmap? I am happy to submit a PR for the feature.