Reading and writing tickets

When Andy works on a task in a Space that has a Jira project linked, it can pull ticket content into the conversation and write back to Jira when the work is done. This usually happens as part of a regular Slack conversation or web app task, not as a separate Jira-only flow.

Reading a ticket

You bring a ticket into a conversation by referencing it the way you normally would — pasting the ticket key (PROJ-123) or a Jira URL into your message to Andy:

@MeetAndy plan PROJ-123

@MeetAndy implement the changes described in https://acme.atlassian.net/browse/PROJ-123

When Andy plans or implements the task, it fetches the ticket from Jira and uses what it finds — title, description, status, assignee, priority, comments, and attachments — as context. The plan Andy posts in Slack reflects what's in the ticket.

You don't have to paste the ticket — you can also describe the work in your own words and let Andy figure out the rest. Pasting the ticket is just a fast way to give Andy the full description.

Updating a ticket

Andy can write back to Jira when it makes sense — most commonly during the Coding Agent flow. The kinds of updates Andy can make:

• Add a comment — for example, summarizing the work done in a PR
• Change status — move the ticket from "To Do" to "In Progress" when work starts, or to "Done" when a PR merges
• Edit description — append progress notes or update implementation details
• Set fields like priority and labels
• Upload attachments — only available on Forge-authenticated Jira sites

Status changes use your Jira workflow's transitions. If you ask Andy to move a ticket to a status that doesn't have a valid transition from the current state, Andy tells you which transitions are available.