Features
A feature is one piece of product work. It has its own people, links and memory.
A feature is one piece of product work, like "UPI at Checkout" or "Refunds v2".
Each feature has:
- its people: Admins, Managers and Users,
- its links to your tools: docs, tickets, channels, repos and boards,
- its own memory, built from what happens in those tools.
Create a feature
- Open Features.
- Click + Add new.
- Type a name and click Create.
Anyone in the org can create a feature. You become its Admin.
If you run more than one workspace, pick the workspace too. A User's new feature goes into the org's first workspace.
Add people
Open the Participants panel on the feature.
- Type an email and click Check.
- Someone already in the org: click Add (name) to this feature.
- Someone new: click Invite by email. They get an email. At their first sign-in, they land on this feature.
Admins and Managers of the feature can add and remove Users. Only Admins can make someone an Admin or a Manager.
New people are also added to the feature's Slack channels (matched by work email). They are invited as viewers to its Miro boards.
Only the feature's people can open it
Being an Admin of the org is not enough. Someone on the feature must add you. See Roles and permissions.
Link the work
Click + Add on the feature. You can add:
- a pipeline stage,
- the feature's chat (a Slack channel),
- a Confluence doc,
- a Jira epic,
- a GitHub repo,
- a Figma file,
- a Miro board,
- any other link.
Inside a stage you can also add Bitbucket, Zoom, Microsoft Teams, Notion and Google items.
Everyone on the feature sees what SeamTrail learns from what you link. See Links.
Stages
Stages are optional. They split the work into steps, like Design, Build and Release.
- Add, rename, reorder or remove stages.
- Inside a stage, add team folders and steps. They can sit inside each other.
- Link items at any level: the feature, a stage, a folder or a step.
What the feature page shows
| Part | What it shows |
|---|---|
| Summary | Where the feature stands, in a few lines. |
| Progress | Tasks done per team, and how far their code went: merged to dev, on stage, in prod. |
| Drift | What a change made out of date. See Drift. |
| Recent changes | New decisions, blockers, risks and status changes. |
| Suggestions | Tickets your docs and chats mention that are not on the feature yet. See Links. |
| Plan | Match tickets to the spec, or propose new ones. See Links. |
| History | What used to be true, and what replaced it. See Memory. |
| Promotion rules | What must wait for what before a deploy. See Promotion rules and deploy gates. |
The tabs (Drift, Recent changes, Suggestions, Plan and History) show up only when they have something to show.
Daily digest
A feature with a Slack channel can post a short summary there once a day: each team's progress and the open drift count.
A feature's Admin or Manager turns on Daily digest to Slack on the feature page. It is off until someone turns it on. It posts at 09:00 India time.