How to integrate Jira with Sally AI

Connect Sally AI with Jira to turn what came out of a meeting into tickets people can work on, right in the matching project, issue type and workflow. With the Sally Jira integration you create tickets, add comments and update the status of existing issues in one click, so nothing gets typed twice and your backlog stays current.

Quick navigation

1. How to connect Jira with Sally AI
2. How to send insights to Jira
   • 2.1. Create a ticket in Jira
   • 2.2. Add a comment to a Jira ticket
   • 2.3. Change ticket status with comment
3. Required OAuth scopes

1. How do I connect Jira with Sally AI?

Follow these steps to enable the Sally Jira integration.

1. Open Settings from the bottom-left corner of the sidebar.

Figure 1: Open Settings

2. Under Configuration, select Integrations. If no integration is connected yet, click Discover integrations, otherwise click Add integration in the top right corner.

Figure 2: Open the list of integrations

3. In the Add integration panel, pick the Project management category on the left and then Jira. Complete the authorization on the Atlassian side.

Figure 3: Select Jira

4. After the authorization, Jira appears in the list under the Project management category. Disconnect in the top right corner ends the connection whenever you need to.

---

1.1. Which actions may Sally use?

A connected integration has two tabs, Overview and Actions. The Actions tab defines what Sally offers through this integration, in the Sally chat and after the meeting.

Figure 4: Enable the actions of the integration individually

Primary actions are what Sally does through the integration, meaning listing and retrieving issues, creating and updating them, commenting, and changing the status. Each action explains what it does in the line below it.

Use the toggle on the right to take out a single action that Sally should not use for this organization account.

Not every action shows up in the selection at the meeting. Sally uses some of them itself, in the chat or as part of another action. Leave them switched on so the integration works in full, and switch off only what Sally really should not do in this organization account.

Below that sit the helper functions, the read and search functions that support the primary actions, for example finding a project or a recipient. They stay locked as long as an active action needs them.

---

2. How do I send meeting insights to Jira?

Once Jira is connected, you can send meeting insights from Sally to Jira with a single click, into the right project, with the matching issue type, and in the right workflow.

You can:

• Create a ticket in Jira
• Add a comment to a Jira ticket
• Change ticket status with comment

Which one should I use?

• Create ticket in Jira for a new backlog item or a bug report.
• Add comment to Jira ticket for context or decisions on an existing issue.
• Update ticket status with comment when the work moves on in the workflow and you want to pass on the reason right away.

2.1. Create a ticket in Jira

Turn a Sally insight into a new issue in Jira.

1. Open the meeting in Sally.
2. In the summary, hover over a block or over a single entry and click the plug icon. In the list, choose Create ticket in Jira under Jira.

Figure 5: Pick the Jira action through the plug icon

3. Fill in the dialog. Organization, Project, Vorgangstyp (the issue type), and Title are required, and the title already comes prefilled from Sally. Responsible and Labels are optional, and you only need labels if your project requires them.

Figure 6: Check the fields and create the issue

4. Use the description field to add details. Sally takes them from the summary where there are any, and you can freely adjust them in the editor.
5. Click Create issue to create the ticket in Jira.

Best practice

Pick the issue type that fits the content, a task for a to-do and a bug for a defect, and assign a responsible person right away. The more complete the issue, the fewer follow-up questions come back later in the backlog.

---

2.2. Add a comment to a Jira ticket

Add meeting context to an existing issue, which is ideal for updates, decisions, or extra notes.

1. Open the meeting in Sally.
2. Click the plug icon on the block or on the entry and choose Add comment to Jira ticket under Jira.

Figure 7: Pick the action for a comment

3. In the dialog, pick the organization and the Vorgang (the issue) the comment belongs to. Both fields are required, and the list shows the issues with their ticket key and title.

Figure 8: Pick the issue, check the comment, and send it

4. The comment field holds the text from the summary, which you can edit in the editor.
5. Click Add a comment to send the comment to Jira.

---

2.3. Change ticket status with comment

Move an existing issue on in the workflow and leave the context from the meeting at the same time.

1. Open the meeting in Sally.
2. Click the plug icon on the block or on the entry and choose Update ticket status with comment under Jira.

Figure 9: Pick the action for the ticket status

3. In the dialog, pick the organization, the Vorgang (the issue), and the new status. These three fields are required, and the available statuses come from the workflow of your Jira project.

Figure 10: Pick the status and update it with a comment

4. The comment field is optional. Sally prefills it from the summary, and you can adjust the text or delete it.
5. Click Update to send the status and the comment to Jira.

---

3. What OAuth scopes does the Jira integration require?

For the integration with Jira, Sally uses OAuth 2.0 for authorization. The following scopes define which areas Sally can access on behalf of the authenticated user.

Disclaimer

1. Sally accesses this information solely to technically establish and maintain the connection to the user account.

2. Sally does not make any autonomous changes. Actions are performed exclusively upon the explicit initiative of the user.

3. API endpoints are only called within the scope of an active action initiated by the user within the platform.

Technical overview of required scopes

Scope	What Atlassian technically allows with this scope	How Sally uses this scope
offline_access	Issuance of long-lived access tokens	Enables a stable connection without repeated login. No Jira data is modified.
read:me	Read access to the authenticated user's profile	Sally reads basic account information for authentication purposes.
read:jira-work	Read access to issues	Sally reads issue information where required within the integration context. No issues are modified.
read:jira-user	Read access to user information	Sally reads user information for display within the integration. No user accounts are changed.
write:jira-work	API permission for issue objects	Part of Atlassian's OAuth model. Sally does not independently create or modify tickets outside explicitly user-initiated actions.