Capabilities / Plans
Sending and exporting
Sending creates the plan's work in your project tool, once. Exporting gives you a file. Both start from Send to in the plan drawer.
Send to
Send to sits in the plan drawer's top bar. The main button sends to your last-used tool; its arrow lists Jira, Linear and Asana, then the export formats. A tool you have not connected shows Connect: pick it, connect, and Sands goes straight to that tool's preview.
You can also send from chat:
Try asking
Send this plan to Linear
The preview
Before anything is created, Sands shows how the plan maps to the tool: what each part becomes, how many items will be created, where they will go, and which details the tool will not receive. Choose the project or team to send to, then confirm.
| Plan | Jira | Linear | Asana |
|---|---|---|---|
| The plan | Goes into a project you pick | A new project | A new project |
| Workstream | Epic | Milestone | Section |
| Ticket | Story | Issue | Task |
The preview names any blockers, like a project that has not been chosen, and you can fix them before sending.
What your tool receives
Titles, descriptions and dates go to your tool where it has a place for them; the preview says which. These stay in Sands today and the preview lists the ones your plan has:
- Owners. Assign them in your tool, or ask Sands to assign tickets once they exist.
- Priorities. Items are created with the tool's default priority.
- Estimates and acceptance criteria.
- Dependencies between tickets. Nothing in the tool enforces their order.
After sending
Sands creates the work, reads it back, and replies with a table of everything it created, each with a link. If an item fails, the table says which and why.
Sending again is safe
Sands remembers what each plan created. Sending the same plan again skips what already exists, so you never get duplicates.
A send is a one-time handoff. Later edits to the plan in Sands do not change the items in your tool, and changes in your tool do not flow back into the plan. To change work after sending, ask Sands to update the tickets themselves.
In Manually approve and Automatically approve, a send always waits for your OK. See Approvals.
Exporting
| Format | What you get |
|---|---|
| Word | A .doc file of the whole plan. |
| Opens your browser's print dialog. Choose Save as PDF. | |
| Markdown | A .md file. Copy as Markdown in the title menu puts it on the clipboard instead. |
| Backlog (CSV) | The ticket table as a spreadsheet file. |
Exports are in the Send to menu and under Export in the title menu. A plan can be exported while Sands is still drafting it.