Check every pull request against its Jira ticket.
Mesrai reads the linked Jira ticket — title, description and acceptance criteria — and checks the pull request against each requirement before it merges. Missing behaviour and scope drift show up as review comments, each traced to the exact line of the ticket it comes from.
- Jira
- Cloud + Data Center
- Git platforms
- GitHub · GitLab · Bitbucket · Azure
- Runs
- Every PR + on demand
- AC-1 Refund is prorated to the unused days of the plan
- AC-2 Refunds above ₹50,000 require finance approval
- AC-3 Customer receives a refund confirmation email
AC-2 is not implemented: createRefund() issues refunds of any amount without an approval step. Add the finance-approval check before calling the payment provider.
- 01
Reviewers read the diff, not the ticket. Code that compiles, passes tests and looks clean can still do the wrong thing for the business.
- 02
Acceptance criteria live in Jira while the code lives in your git platform, so checking one against the other is manual work that rarely happens on busy days.
- 03
Scope drift goes unnoticed: a PR quietly implements half a story, or adds behaviour nobody asked for.
- 04
The most expensive bugs — wrong prices, missing approval steps, skipped notifications — are business-logic bugs that no linter or static analyser looks for.
Requirement-by-requirement checks
Each acceptance criterion in the ticket is compared with the PR diff. Mesrai reports which criteria are implemented, which are missing and which contradict the ticket.
Findings traced to the ticket
Every finding quotes the exact requirement it comes from, so reviewers can see why it was raised and verify it in seconds instead of re-reading the whole story.
Severity you can act on
MUST_FIX marks a required rule that is missing or wrong. SUGGESTION flags an uncovered edge case. INFO is a useful observation that doesn't block compliance.
Honest about thin tickets
Mesrai grades the ticket first. A ticket with acceptance criteria gets a thorough check; a title-only ticket gets a conservative one, and an empty ticket gets a request for more information instead of guesses.
On demand, in the PR
Post @mesrai -v business-logic with a Jira link in the main PR comment box to validate any time, including against a different ticket or an inline spec.
Context for the whole review
With Jira connected, Mesrai Rules can fetch task context, check issue status and cross-reference requirements while the normal code review runs.
- 01
Mesrai fetches the pull request diff and its metadata.
- 02
It retrieves the linked Jira ticket through your connected Jira plugin.
- 03
It grades how complete the ticket is — complete, partial, minimal or empty — which sets how deep the check goes.
- 04
It compares the implementation with each acceptance criterion.
- 05
It posts findings in the pull request with a severity and the requirement each one traces back to.
Jira is connected once per workspace as a plugin. After that, business logic validation runs automatically on every review — it's on by default.
- 1
In Mesrai, open Settings → Plugins.
- 2
Find Jira and click Connect, then authorize access to your Jira workspace.
- 3
Choose which Jira projects Mesrai may read.
- 4
Open a pull request that references a ticket — or comment @mesrai -v business-logic with a ticket link.
- Jira editions
- Jira Cloud and Jira Data Center
- Access
- OAuth or API token, read access to the projects you select
- Turn on or off
- reviewOptions.business_logic in mesrai-config.yml, or Code Review Settings → Analysis Types
- Other sources
- Linear, Notion, ClickUp, Google Docs and Slack links through plugins — or paste the spec inline
- Pricing
- Every feature is free for 14 days with no credit card. After the trial, Pro is ₹499 / $6 per developer per month on your own LLM key (BYOK) — you pay your AI provider directly, with no markup.
Which git platforms does Jira validation work with?+
Business logic validation runs inside Mesrai's normal pull request review, so it works on every platform Mesrai supports: GitHub, GitLab, Bitbucket and Azure DevOps. The Jira connection is per workspace, not per repository.
Does Mesrai support Jira Data Center as well as Jira Cloud?+
Yes. Mesrai supports Jira Cloud and Jira Data Center, connected with OAuth or an API token. It needs read access to the projects you want validated.
What if our tickets don't have acceptance criteria?+
Mesrai grades the ticket before checking the code. With a title and description but no criteria, it does a best-effort check from the described behaviour. With only a title, it flags only obvious gaps. With no meaningful content, it asks for more information instead of guessing.
Can I validate a PR against a spec that isn't in Jira?+
Yes. Comment @mesrai -v business-logic followed by a link to a Linear issue, Notion page, Google Doc or Slack thread your plugins can reach — or paste the requirements directly in the comment. No plugin is needed for inline specs.
Can I turn business logic validation off for one repository?+
Yes. Set reviewOptions.business_logic to false in that repository's mesrai-config.yml, or toggle Business Logic under Code Review Settings → Repository → General → Analysis Types.
Try Mesrai on your next pull request.
14-day free trial · every feature unlocked · no credit card required.