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.
Ray is on Slack today. Free to start, and nothing sensitive happens without your approval.
- 50 free tasks to start, then 25 a month free
- No credit card
- Nothing sensitive without your approval
How it goes now
The version of this everyone recognises, and nobody has time to fix.
- 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
No builder, no workflow to configure, and nothing that acts on its own.
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.
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.
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.
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
Somebody says something. Ray does the rest, and asks before anything leaves the room.
“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.
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.
Asana
ClickUp
Trello
Todoist
Notion
What Ray does not do here
Worth knowing before you try it, rather than after.
- 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 people ask first
The short answers are here. If we have not covered something, just ask.
Add Ray to one channel and hand it something.
Free to start, no card, about two minutes. Ray sees only the channels you invite it to.