Check a pull request against its Jira ticket
With Jira connected, Solemly reads the ticket linked to every pull request and reports a Solemly / Acceptance check: Matches the Jira ticket, or Incomplete with the requirements not yet done. It judges completeness only. Code quality stays in the review, and the check can be made required to hold a merge until the work is finished.
Checked against the product on 2026-11-03.
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, such as
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, and it doesn't affect the acceptance verdict.
| 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.
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, and the token. - Click Connect Jira. Only workspace admins can connect integrations.
Solemly reads Jira as the account that owns the token, so it can only see projects that account can see. A shared service account with read access to your projects works well.
Make it a merge gate
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 on your code host, the same way as the review check. See Block a merge on AI code review findings.
Questions
Does the acceptance check affect the code review?
No. It judges completeness only: whether the change does what the ticket and its acceptance criteria ask. Code quality is the review's job, and the review doesn't affect the acceptance verdict.
What if a pull request has no Jira ticket?
Nothing is evaluated. On GitHub the pull request gets a neutral Solemly / Acceptance check; on GitLab and Bitbucket it gets no acceptance status at all.
Which Jira does it connect to?
Your Atlassian site, such as your-team.atlassian.net, with an API token created at id.atlassian.com. Solemly reads Jira as the account that owns the token, so it sees only the projects that account can see.
Can it block a merge when the work is incomplete?
Yes, if you make Solemly / Acceptance a required check. It fails on incomplete work whatever the repository's blocking setting, but it only blocks a merge when it's required.
In the docs
Related
Try it on your next pull request
Free for 14 days with every feature, no credit card. Install it on a repository and the next pull request gets reviewed.