Once a project is analysed, Specsight keeps your spec current on its own. Every release on the watched branch triggers a sync.
A sync updates only the features the release affected. The rest of your spec is left alone, including anything you added or edited by hand.
What a sync changes
- Scenarios — added, updated or removed wherever behaviour changed
- Feature descriptions — rewritten when they no longer match the code
- The user flow — redrawn for each affected feature
- Changes — a new entry, with the wording before and after on each change
When nothing changed
Not every release changes behaviour. A refactor or a formatting pass changes nothing your users would feel.
Specsight records those as a Specsight reviewed entry in Changes. You can see the release was checked, not skipped.
A release can fix something without changing any scenario. Its reviewed entry then lists what it fixed, and members are notified as for any release.
How you know a sync ran
Your spec stays readable while a sync runs, and an indicator on the project page shows one is in progress.
When a sync changes or fixes something, every member gets an in-app notification. An email goes to anyone with Sync complete switched on in account notifications.
The email shows the release’s summary and what it changed, as its page does, with each Highlight tagged by type. Click See the release to open it.
Limits
Standard allows 200 syncs a month. See plans and limits.
When your organisation reaches it, syncs pause until the period renews. One sync then catches up on everything merged meanwhile. Admins get an email at 80% and when syncs pause.
Stop automatic syncing
Open Integrations, pick your connection and click Disconnect. Syncing resumes when you connect again.