# Create a Jira ticket from Slack, without leaving the thread

> Chat becomes a real ticket, in your tracker. How it works, what it looks like in a channel, and what Ray does not do here.

Source: https://heyray.io/use-cases/tickets-from-chat

The work was already described. Stop retyping it.

Somebody explains what needs doing, in a channel, in their own words. Ray turns that into a properly formed ticket in the tracker you already use, keeps the original message attached to it, and shows you the card before anything gets filed.

## How it goes now

- Work gets described perfectly well in a thread, then written again, worse, in a ticket an hour later.
- The person who understood the request is not the person who files it, so half the context does not survive the trip.
- Whoever files it copies a wall of chat into the description field, and nobody reads it again.
- The things nobody had time to file are the things that get remembered on the day they were due.

## How it actually works

1. **Say what you want, in the channel.** No command to learn and no syntax to get right. Ray reads the channels you invite it to and works out that this one is a request.
2. **Ray writes the ticket, rather than copying the thread.** A real title, a description someone can act on, and the asker's own message kept as context. It fills in what the tracker needs, including the project and the assignee when the thread makes those clear.
3. **You see it before it exists.** Creating a ticket is a write, so it waits. Ray posts a card in the channel showing the title, the description and where it is going, and nothing is filed until somebody taps Approve.
4. **The link comes back to the thread.** The ticket is posted where the conversation happened, so the person who asked can see it landed without going looking.

## What that looks like in a channel

**"The export button on the billing page 500s if the date range is over a year."**

Ray writes it up as a bug with steps to reproduce taken from the thread, sets the project, and shows you the card before it files.

Tools: Jira, Linear, GitHub, GitLab

**"Can someone pick up the onboarding email copy before Thursday?"**

Ray files it with Thursday as the due date and the requester recorded, and asks who should own it if the thread never said.

Tools: Asana, ClickUp, Trello, Todoist

**"File everything Priya listed above as separate tickets."**

Ray reads back up the thread, splits the list into one ticket each, and shows you all of them on a single card to approve together.

Tools: Jira, Linear, Asana, Notion

## The tools this touches

Jira, Linear, Asana, ClickUp, Trello, Todoist, GitHub, GitLab, Notion, Basecamp, Wrike, Productboard

Every one has its own page saying what Ray reads there and what waits for an approval. The full set is at https://heyray.io/integrations.md

## What Ray does not do here

- Ray files tickets, it does not run your board. Sprints, swimlanes and workflow states stay where they are, and Ray reads them rather than replacing them.
- It will not invent an assignee or a priority the conversation never mentioned. If the thread does not say who owns it, Ray asks rather than guessing.
- Ray is on Slack today. Discord, Teams and Google Chat are not shipped yet.

## What it costs

Free covers 25 tasks a month plus a one-time 50-task starter grant that never expires. Pro is one flat price for your team size: $49 a month for 1 to 3 people, $99 a month for 4 to 10 people, $199 a month for 11 to 25 people. No seats, and using Ray more never costs more. Failed work is never counted and never billed.

## What people ask first

**Does this need a slash command?**

No. Ray reads the channels you invite it to and works out when something is a request. You can also just ask it directly if you would rather be explicit.

**What if it writes the ticket badly?**

You see the card before anything is filed, with the title and the full description on it. Reject it and tell Ray what was wrong, in the thread, and it rewrites it.

**Can it file into more than one tracker?**

Yes. Ray works with whichever of them your team has connected, and it can file into different ones from the same channel if that is genuinely how you work.

**Does the original message stay attached?**

Yes. The asker's own words go on the ticket, which is usually the part that gets lost when a human retypes a request.

**Who can approve a ticket being created?**

Anyone in the channel. The approval runs as the person who taps it, using their own connected account, so your tracker's permissions are the ones that apply.