Integrations
Jira
Sands' deepest connection: read projects and issues, work the board from chat, build hours reports from worklogs, and send plans as epics and stories.
What Sands can do
| Action | What it does | Try asking |
|---|---|---|
| List projects | Lists the projects you can see. | Show me my projects |
| List workstreams | Lists a project's epics. | What epics are in WEB? |
| Find work | Searches by project, person, status or text, sorted the way you ask. | Show me open issues assigned to me |
| Summarize a ticket | Summarizes one ticket with its description and comments. | Summarize WEB-142 and its comments |
| Project health | Open work, recent completions, overdue and blocked items. | How is WEB doing? |
| Retrospective | What finished and what stalled over a window, with computed counts. | Retro on WEB for the last two weeks |
| Worklogs | Builds an hours table from worklogs. | Hours report for WEB for September |
| Create | Creates an issue. | Create an issue in WEB to fix the coupon field |
| Assign | Sets who owns it. | Assign WEB-142 to Dana |
| Move | Moves an issue to another status in its workflow. | Move WEB-142 to In Review |
| Edit | Changes fields like title, priority or due date. | Set WEB-142 to High priority, due Friday |
| Comment | Adds a comment with your words or facts read from your tools. | Comment on WEB-142 that the fix is on staging |
| Log time | Logs hours on an issue. | Log 2 hours on WEB-142 for code review |
| Create a project | Creates a project. Pauses for your OK in Automatically approve. | Create a Jira project called Website Relaunch |
| Receive a plan | Creates each workstream as an epic and each ticket as a story in a project you pick. | Send this plan to Jira |
Examples
Try asking
Show me open bugs in WEB assigned to me
Try asking
Move WEB-201 to In Progress and assign it to Dana
Try asking
Hours report for ACME for September, grouped by component
Use case examples
Setup
Start the connection
Click + in the composer and choose Jira, or open Settings → Connectors.
Approve in Atlassian
Atlassian's sign-in opens in a pop-up. Choose the site to grant and approve. Sands works with what your Atlassian account can see on that site.
Start asking
Back in Sands, Jira shows as connected. Ask about any project you can see.
Permissions
- Sands acts as you, with your Jira permissions. It cannot see or change anything you cannot.
- Your token is stored encrypted against your Sands account. Sands never sees your password.
- Confluence access is part of the same Atlassian grant; Sands does not use Confluence yet.
Good to know
- Jira Cloud only.
- Plans go into an existing project. If you need a new one, ask Sands to create it first, or create it in Jira.
- Owners, priorities, estimates and dependencies in a plan stay in Sands when you send it. See Sending and exporting.
- Large projects take a little longer to read: Sands keeps within Jira's rate limits.
More in Sending and exporting and Hours reports.
Troubleshooting
| What you see | What to do |
|---|---|
| Sands asks you to reconnect | Atlassian access expired. Click Reconnect; the request resumes. |
| A project is missing | Check it is on the site you granted, and that your Atlassian account can see it. |
| A move to a status fails | That status is not reachable from the issue's current status in its workflow. Sands lists the statuses it can move to. |
Still stuck?
Use the feedback button in the sidebar with the chat open; the run shows us exactly what happened.