Use cases and guides / By team
Sands for engineering teams
Engineering leads use Sands to turn design docs into tickets, see what is blocked, and keep the board current without leaving the conversation.
At a glance
| Job | Try asking | Works with |
|---|---|---|
| Turn an RFC into tickets | Turn this RFC into a plan for the platform team and send it to Jira | Files, Jira, Linear, Asana |
| Find what is blocked or overdue | What is blocked or overdue in PLAT right now? | Jira, Linear, Asana |
| Work the board in plain language | Move PLAT-142 to In Review and assign it to Sam | Jira, Linear, Asana |
| File bugs from a Slack thread | Read the thread in #qa about checkout and create a ticket for each bug in WEB | Slack, Jira, Linear, Asana |
| Run the sprint retro | Retro for the last two weeks of PLAT | Jira, Linear, Asana |
Use cases
1. Turn an RFC into tickets
Attach the design doc. Sands drafts the workstreams and tickets with owners, estimates and dependencies, then sends them to your tool.
Try asking
Turn this RFC into a plan for the platform team and send it to Jira
More: Plans
2. Find what is blocked or overdue
Sands reads the board and lists the blocked and late work with owners and links.
Try asking
What is blocked or overdue in PLAT right now?
3. Work the board in plain language
Create, assign, move, edit and comment on tickets by asking. Each change is read back after it runs.
Try asking
Move PLAT-142 to In Review and assign it to Sam
More: Work in your tools
4. File bugs from a Slack thread
Point Sands at a thread of bug reports and it creates one ticket per bug with the details from the messages.
Try asking
Read the thread in #qa about checkout and create a ticket for each bug in WEB
More: Messaging
5. Run the sprint retro
What shipped, what slipped and where the load sat, from completion data.
Try asking
Retro for the last two weeks of PLAT
Recommended setup
- Connect Jira, Linear or Asana.
- Install Sands in Slack and add it to your team channels.
- Use Automatically approve; switch to Manually approve on boards other teams depend on.
Where to go next
Quickstart, Approvals, or the other use case guides.