Changes is your project’s changelog: every change, newest first. Open Changes in the project rail.
What shows up here
- First analysis — where your changelog starts, with the features and scenarios Specsight found. After a re-analysis it reads Re-analysis
- A release — its title, its Highlights, a short summary, how many changes are new, changed, gone and fixed, and the features it touched
- Specsight reviewed — a release that changed no scenario, with a short reason or what it fixed
- Manual edits — when someone adds, edits or deletes a scenario by hand
- Annotations — free-text notes someone left on a scenario
A run of consecutive reviewed releases collapses into one row you can expand. A review that fixed something keeps its own row.
What changed in a release
Click an entry to open that release. It starts with what changed for the people using your product, in up to four lists:
- New — what people can do now that they couldn’t before
- Changed — what works differently, moved or was renamed
- Gone — what people can no longer do or find
- Fixed — what used to go wrong and now works
Under All changes, each feature the release touched has a line on what changed. A feature the release created is tagged New feature.
Click a feature for its scenarios, with the old wording struck through above the new. Click Show all to open every feature, and a scenario to open it in the spec.
When a release is worth telling customers about, click Draft release notes on its entry. Release notes opens with that release’s changes already picked.
To ask about one release, click Ask about this release and pick a question. Ask Specsight answers about that release only.
Which changes matter to your customers
A Highlight is a change that sales, support or marketing should know about. Each one has a type, shown on the change it belongs to. Specsight sets Highlights during a sync, and most releases have none.
Highlight types
- Heads-up — something people already use works differently, moved, was renamed or is gone
- Pricing — what a plan costs or includes, a trial, or how billing works
- Limits — how much everyone can do, like a quota or a file size
- Privacy — what happens to people’s data: what’s collected, shared, exported or kept
- Security — how people sign in or how accounts are protected
- Access — who can see or do something, by role or by plan
- Integrations — how the product connects to other tools
- Beta — something only some customers can see so far
- News — a new capability worth announcing
Open a release and hover a type to see who should act on it.
Where Highlights show up
- On Changes — each release shows its kinds of Highlight next to its title
- On the release page — tagged with its type on the list item that names the change
- On Overview — its type on the release’s card, and what it says when you hover the card
- On the organisation home — each project card shows the count from its latest release
- In the sync email — tagged with its type on the change that names it, as on the release page
- In Ask Specsight and MCP — entries carry the Highlight, its type and its reason
Find a specific change
Filter the feed by source: All, Specsight, Manual or Annotations. Specsight covers synced and reviewed releases and the analysis. To see one feature’s changes, pick it in All features.
Search matches a release title, a scenario, a feature name, an author, or the text of a summary or note.
Click Load earlier changes for older history.
What happened to one scenario
Open a scenario in the spec: its panel has a History section listing every event that touched it. Use it when you want the trail for one behaviour rather than the whole project.
What shipped lately
Overview shows the last seven days of releases, day by day. Click one to open it.
When the first of those days had no release, it shows the last one before them instead. A day with more than two releases links to the rest in Changes.
For a summary of everything that changed over a date range, use digests.