Skip to main content
The Jira integration makes delivery status available in your client work. Ask what is blocked on an engagement, what shipped this sprint, or how much time went into an epic, and Hebno answers from Jira with each issue cited. When a request implies a change, such as raising an issue or moving one to Done, Hebno shows a confirmation card and writes to Jira only after you confirm.

​
At a glance

​
Before you start

You need:
  • An Atlassian account with access to the Jira Cloud site you want to use.
  • An allowed integration. An owner or admin sets Jira to Allow under Admin → Connectors → Catalogue.
  • Approval from your Atlassian organisation admin if they require approval for third-party apps.
Hebno requests these OAuth scopes:

​
Connect Jira

1

Start the connection

Open Settings → Connections, find Jira and select Connect. You can also select Connect from the prompt in a chat.
2

Choose your site

Sign in to Atlassian, choose the Jira site, for example northwind.atlassian.net, and select Accept.
3

Return to Hebno

The card shows Connected with the site name.
Hebno reads and writes with your own permissions, so you see only the projects and issues that your Jira permission schemes and issue security levels allow. Tokens are encrypted at rest. Select Disconnect at any time, or ask an admin to revoke the connection under Admin → Connectors → Connections.

​
What Hebno reads

Hebno searches Jira with JQL, for example project = CTO AND status != Done ORDER BY priority DESC. You can paste your own JQL into a request and Hebno runs it as written. Reads are live. Hebno queries Jira when a request needs it. Only what a reply used is stored with the conversation as its sources.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including issue descriptions and comments from Jira.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Jira with editable fields

A Jira change pending confirmation. Nothing is written until you confirm.

Hebno never deletes issues, changes workflows, permissions or project settings, or edits issues in bulk. Writes are made as your Atlassian user, so Jira shows you as the author. If a field is required by the project but missing from your request, you are prompted for it on the card before you can confirm. Linking marks which Jira project belongs to an engagement, so you can ask “what is blocked?” without naming it.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Jira.
  3. Search by project key or name and select it. Repeat if the engagement spans several Jira projects.
In chats tagged to the project, Hebno starts with the linked Jira projects for any delivery question, and cards for new issues default to them. See Linked records.

​
Use Jira in chat

  • Attach: open the + menu, choose Sources → Jira, and pick an issue, epic or sprint. Or type / and choose Jira.
  • Ask: name the ticket, epic or sprint in your request. For example:
    Summarise what shipped in the last two sprints on the Contoso data migration, and list what is still blocked.
    Draft a weekly status update for Contoso from the open issues in CTO, grouped by epic.
    Log 2 hours on CTO-142 for yesterday with the note “Reviewed export logic with the client team”.
  • Research runs show a Checking Jira step, with a chip for each issue it read.
  • Agents can read Jira on a schedule, for example a Friday summary of overdue issues. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting