Jira
Check every pull request against its linked Jira ticket.
With Jira connected, Solemly checks every pull request against its linked ticket: does the change do what the ticket asks? It's reported on its own Solemly / Acceptance check.
Connect Jira#
- Create an API token at id.atlassian.com → Security → API tokens.
- In Solemly, open Integrations → Jira and enter:
- your site, such as
your-team.atlassian.net - the email of the Atlassian account that owns the token
- the API token
- your site, such as
- Click Connect Jira. Only workspace admins can connect integrations.
How the ticket is found#
Solemly looks for a Jira key, such as PROJ-123, in this order and uses the first one it finds:
- the branch name, e.g.
feature/PROJ-123-add-retries - the pull request title
- the pull request description
Strings that look like keys but aren't tickets, such as UTF-8 or SHA-256, are skipped. The key must exist in your Jira site.
What it checks#
The acceptance check judges completeness only: whether the change does what the ticket and its acceptance criteria ask for. Code quality is the review's job. It doesn't affect the acceptance verdict.
Results#
| Result | Meaning |
|---|---|
| Matches the Jira ticket | The change does what the ticket asks. |
| Incomplete vs. PROJ-123 | Some requirements aren't done yet. The check lists them, under Not yet done in this PR according to PROJ-123. |
| No linked Jira ticket | No key was found, or the ticket couldn't be read. Nothing is evaluated. |
On GitHub, a pull request with no linked ticket gets a neutral Solemly / Acceptance check. On GitLab and Bitbucket it gets no acceptance status at all, and when there is a result, the missing requirements are added to the review comment.
The acceptance check fails on incomplete work whatever the repository's blocking setting. It only blocks a merge if you make Solemly / Acceptance a required check. See Merge Gates.
Something missing or unclear? Tell us.