Drift
When a doc section or a decision changes, SeamTrail flags the tickets and pull requests that are now out of date.
Drift is work that a change made out of date.
Example: the spec said "refunds within 7 days". Someone edits it to "3 days". The ticket built for 7 days, and its open pull request, are now out of date. SeamTrail flags them.
What starts a drift check
- A doc section changes. Someone edits a section of a linked Confluence page, or a frame on a linked Miro board.
- A decision is made, anywhere. In a Slack message, a Jira description or comment, a meeting summary, a pull request comment, or an AI assistant's note.
A decision counts when it changes what a doc section says, or names the tickets it affects.
How SeamTrail checks
- Did the meaning change? A typo fix or a reworded sentence stops here. Nothing is flagged.
- What was built on it? SeamTrail looks at the tickets linked to that section: their descriptions, comments, status and environment. It also looks at their pull requests.
- What is out of date? Each item gets a label and a reason:
- stale: now out of date.
- check: worth a look.
When a decision changes what a doc says, the doc section itself can be flagged too.
A decision written by an AI assistant also starts a check. It is marked unconfirmed until a person confirms it.
Where you see it
| Place | What you get |
|---|---|
| The feature's Drift tab | What changed, who changed it, where it was said, what is affected and why. |
| A ticket's brief (the ⓘ on a ticket) | The open drift on that ticket. |
| Your AI assistant | Open drift is part of the feature's status and context. The drift on your own tickets is listed for you. |
| The SeamTrail chat | Answers name open drift when it matters. |
In the Drift tab, click Mark handled when the work is updated. Click Not related when the flag is wrong. Show history shows closed drift.
Who is told
The people who own the affected tickets see the drift in their own view: in SeamTrail, and in their AI assistant's context.
Drift is shown, not sent. SeamTrail does not post drift to Slack channels or to pull requests, and it writes nothing into Jira.
What drift needs
When a doc section changes, drift reaches a ticket through the link between that ticket and the section. A ticket with no link to the section is missed. SeamTrail makes most of these links by itself. See Links.
A decision also checks the tickets it names, even without a link.
SeamTrail does not read your code. It flags the linked pull requests. Your coding assistant can read the code.
How fast
- Chat, tickets and code: as soon as the tool sends the change.
- Confluence: SeamTrail checks linked pages for changes every few minutes. Click Update memory on a feature to read its docs right away.
Coming soon
- Drift from edits in Notion pages and Google Docs.
- Drift from edits in Figma designs.
- Decisions in meeting transcripts, GitHub code-line comments and Bitbucket pull request comments.