Capabilities
Work in your tools
Ask Sands to change work in Jira, Linear or Asana the way you would ask a teammate. It makes the change, reads it back, and links to it.
What you can ask for
| Action | Example | Jira | Linear | Asana |
|---|---|---|---|---|
| Create a ticket | Create a task in WEB to fix the coupon field | Yes | Yes | Yes |
| Assign | Assign WEB-142 to Dana | Yes | Yes | Yes |
| Move to a status | Move WEB-142 to In Review | Yes | Yes | Between sections, or complete |
| Edit fields | Set WEB-142 to High priority, due Friday | Yes | Yes | Yes |
| Comment | Comment on WEB-142 that the fix is on staging | Yes | Yes | Yes |
| Log time | Log 2 hours on WEB-142 for code review | Yes | ||
| Create a project | Create a Jira project called Website Relaunch | Yes | Yes | |
| Update a project | Set the Onboarding project's lead to Ana | Yes |
Several changes can go in one message. Sands does each one and reports each result.
Try asking
Create tickets in WEB for the three bugs above, assign them to Sam, and mark them High priority
How changes run
- Your approval mode decides whether a change runs right away or waits on an approval card.
- Sands acts on the exact ticket or project you named. If a name matches more than one, it asks which.
- After the change, Sands reads the item back and reports what actually landed, with a link.
- A change runs once, even if you retry the request.
- Statuses follow the workflow: if a status cannot be reached from where the ticket is, Sands lists the ones it can move to.
Comments and text
Comments Sands posts contain your words or facts it read from your tools. Ask it to post research and it builds the comment from the search it just ran. When a change carries text, the approval card shows the whole text.
Why this rule
A comment on a client's ticket is durable and visible. Sands never puts claims there it cannot back up.