Baselines, Views, Comments & History
Baselines, Views, Comments & History
Baselines (Specification Snapshots)
A baseline is a named, read-only snapshot of a specification at a specific point in time. Once you create a baseline, it captures the exact state of the specification — which requirements existed, in what order, and at what hierarchy level — and preserves it permanently for reference.
Baselines are useful for:
Locking a specification at a project milestone or release
Providing an audit trail of how requirements evolved
Comparing the current state of a specification against a previous version
Creating a Baseline
Right-click any requirement row in the specification table.
Choose Baselines from the context menu.
In the Baselines panel, click Create.
Give the baseline a name (e.g. "Release 1.0 freeze") and an optional description.
Confirm to save.
The baseline is stored immediately and appears in the baseline list.
Viewing a Previous Baseline
Open the Baselines panel (right-click → Baselines).
Click on a baseline name from the list.
The specification opens in read-only snapshot mode, showing the requirements exactly as they were when the baseline was created.
Deleting a Baseline
In the Baselines panel, select the baseline you want to remove and click Delete. This removes the snapshot but does not affect the current specification or any Jira issues.
Baseline Comparison Mode
When a specification is open, you can select a baseline from the left sidebar to enter comparison mode.
In comparison mode:
The current requirements are shown alongside the baseline state.
Requirements that were added, removed, or changed since the baseline are visually highlighted so differences are easy to spot.
The baseline side is read-only — you can view it but not edit it.
This mode is ideal for reviewing what changed between a snapshot (e.g. a signed-off version) and the current working state of the specification.
Saved Views
A saved view is a named column configuration for the requirements table. Instead of reconfiguring which columns are visible every time you open a specification, you save your preferred setup as a view and switch between views instantly.
Views control:
Which columns are visible (custom fields, system fields, link columns)
The order of those columns
View Types
Type | Who can see it |
|---|---|
Private | Only you |
Public | All users of the project |
Type-based | Linked to a specific artifact type — only applies when viewing specifications of that type |
Creating and Managing Views
The Views panel is in the left sidebar of any open specification.
To activate a view: Click its name in the list.
To create a new view: Configure the columns you want visible in the table, then click Create View in the Views panel. Give it a name and choose whether it is private or public.
To edit a view: Activate the view, adjust the columns, then save.
To delete a view: Select it in the Views panel and click Delete.
The app remembers which view was last active for each specification, so your preference is restored the next time you open it.
Comments
To see or add comments on a specific requirement:
Right-click the requirement row in the table.
Choose View Comments from the context menu.
A comments panel opens, showing all existing Jira comments on that requirement's issue.
To add a new comment, type in the input field at the bottom of the panel and submit.
Comments are stored directly on the Jira issue, so they are visible to anyone who opens the issue in Jira as well.
History (Change Log)
To see a full record of changes made to a requirement:
Right-click the requirement row in the table.
Choose View History from the context menu.
A history panel opens, showing the Jira issue's change log — each entry records who changed which field, what the old value was, and what it changed to, along with the date and time.
This is the same change log you would see if you opened the issue directly in Jira.