# Ray and Jira

> The same ticket craft, in the tracker your company already runs on.

Source: https://heyray.io/integrations/jira

Ray is an AI teammate that works in your team chat, on Slack today. Connect Jira and it can do the Jira part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written. 13 reads run without asking. 5 actions wait for a human approval.

## What Ray reads in Jira

Reading changes nothing, so Ray never stops to ask whether it may look something up.

- Issues, projects, and the people on them
- Your issue types and transitions

## What waits for your approval

Every one of these posts an approval card in the thread showing exactly what is about to happen. Nothing runs until someone clicks approve, and no setting turns that off.

- Create an issue in the right project and type
- Update fields and move an issue through its workflow
- Comment on an issue

## Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

- Delete an issue
- Change project or workflow configuration

## Ask it like this

- "@Ray raise that in Jira under the payments project."
- "@Ray what is in progress on the payments board right now?"
- "@Ray move PAY-88 to done and assign it to Priya."
- "@Ray comment on PAY-88 with what we found."

## Connecting Jira

Every person on the team connects their own Jira account on Jira's own login screen, so Ray can only reach what that person can already reach, and the history in Jira shows who actually asked. Passwords never pass through Ray. Disconnecting Jira or uninstalling Ray revokes the connection.

## More

- This page for people: https://heyray.io/integrations/jira
- Every integration: https://heyray.io/integrations.md
- Install Ray: https://heyray.io/install.md
- Pricing: https://heyray.io/pricing.md