# Send Salesforce findings to Jira, with the evidence attached.

> The SyncOnAI 360 Jira connector, in beta, raises Salesforce audit findings as issues in a Jira Cloud project using an API token you create. Each issue is written from the finding's own record, links back to it, names who raised it, and has its status checked back on demand. Jira Server and Data Center are not supported.

Source: https://synconai360.com/connectors/jira

## Key facts

- **1**: Step from finding to Jira issue
- **Cloud**: Jira Cloud sites only
- **1**: Issue per finding, never duplicated
- **Beta**: Built and tested, early in live use

## Why Salesforce findings get lost on the way to Jira

Teams that plan in Jira copy assessment findings into tickets by hand. The evidence stays behind, the same finding is raised twice, and nobody can tell from the assessment whether anything was done.

- **Copy and paste.** Each finding is retyped into a ticket, and the detail that proves it is left out.
- **Duplicates.** The same finding is raised by two people in two sprints.
- **No way back.** The assessment cannot show which findings have tickets or what state they are in.
- **Anyone can type anything.** A ticket labelled as an audit finding may say whatever its author wrote.

## How does a Salesforce finding become a Jira issue?

Open a finding from the audit and raise it in Jira. The issue's summary and description are written from the finding's own record, its title, detail, severity and section, with a link back to it in SyncOnAI 360, and created in the Jira project you chose when connecting.

Everything written to Jira is read from the finding itself, not typed in the browser, so an issue labelled as coming from an audit always says what the audit found.

- Written from the finding's record
- Links back to the finding
- Created in your chosen project

## How are duplicate Jira issues avoided?

Each finding can have one Jira issue. If someone tries to raise it again, they are told which issue already exists, with its key, rather than creating a second one.

The link between the finding and the issue is kept, so the finding shows its Jira issue and the issue links back to the evidence.

- One issue per finding
- Existing issue named
- Links kept both ways

## How is Jira status shown in SyncOnAI 360?

Issue status is pulled from Jira on demand, and every status is shown with the time it was checked. There is no live push from Jira, so a status is never presented as more current than it is.

When a finding's fix is deployed and the audit runs again, the finding is marked verified fixed, which is the evidence that the work in the Jira issue actually reached the org.

- Status checked on demand
- Time of each check shown
- Re-audit verifies the fix

## How do you connect Jira to SyncOnAI 360?

An admin enters the Jira Cloud site address, the email of the account, and an API token created in that Atlassian account, then picks the project new issues go into. The token is stored encrypted and is not shown again after saving.

Issues are created as the account whose token was supplied, so Jira shows that account as the reporter. The person in SyncOnAI 360 who raised the finding is named in the issue description so nothing is lost.

- Site, email and API token
- Choose the target project
- Requester named in the issue

## What are the limits of the Jira connector?

It works with Jira Cloud sites only; Jira Server and Data Center are refused rather than half supported. It raises findings as issues and checks their status; it does not sync Jira issues into project boards or edit issues after they are created.

The connector is in beta: it is built and tested, and early in live use. For working with Jira from the chat, the outside tools option can also connect Atlassian's own tool server, with every call recorded.

- Jira Cloud only
- Raise and check, not two-way sync
- In beta

## Connecting Jira

1. **Create a token.** In the Atlassian account issues will be created as.
2. **Connect.** Enter the site, email and token, then pick a project.
3. **Raise.** Send a finding to Jira from the audit.
4. **Check.** Refresh status beside the finding when you need it.

## Findings in Jira, retyped versus raised

| Without | With SyncOnAI 360 |
|---|---|
| Findings retyped into tickets | Issues written from the finding itself |
| Evidence left behind | A link back to the evidence |
| The same finding raised twice | One issue per finding |
| No idea which findings have tickets | Issue and status beside each finding |

## Who uses the Jira connector

- **Delivery managers.** Keep planning in Jira while findings arrive with their evidence and a link back.
- **Salesforce admins.** Send a finding to the team's backlog in one step instead of writing the ticket.
- **Consultancies.** Raise a client's findings in the client's own Jira project, with the evidence attached.
- **Platform teams.** Track technical debt in the tool the wider IT team already uses.

## Frequently asked questions

### Is the Jira integration two-way?

No. It raises findings as Jira issues and checks their status on demand. It does not sync issues into project boards.

### Does it work with Jira Server or Data Center?

No. Jira Cloud sites only.

### Who appears as the reporter in Jira?

The account whose API token was supplied. The SyncOnAI 360 user who raised the finding is named in the description.

### How current is the status shown?

It is checked when you ask, and shown with the time of the check.

### Can a finding be raised twice?

No. Each finding can have one Jira issue, and a second attempt names the existing one.

### Why is it in beta?

It is built and tested, and early in live use. We would rather say so than present it as proven.

### Can project work items link to Jira?

The connector raises audit findings today. Projects in SyncOnAI 360 have their own boards, backlogs and releases.

### Is the token stored safely?

It is stored encrypted and never shown in full after saving. Revoke it in your Atlassian account at any time.

### Is Jira on every plan?

Yes. Every plan includes every feature.

### Can we create an issue that is not from a finding?

Yes. An issue can be typed on the Jira integration page; it is created in the chosen project with the requester named.

### What happens if Jira rejects an issue?

Jira's own error is shown, in Jira's words, so the person can act on it.