[product]
Review the change against the bug or feature it claims to implement.
Task Context brings linked ticket details into review so Autometric can check regression coverage for bugs, walk acceptance criteria for features and tasks, and catch wrong-intent changes earlier.
[task-linked review]
Linked ticket context changes what the reviewer checks.
This is not a generic side panel. The linked ticket changes review behavior, severity, and evidence for the exact pull request under review.
Duplicate charge on payment retry
Expected outcome: second submit reuses the first successful charge and returns the original receipt.
What the ticket demands
- Reuse the original idempotency key when the checkout button is pressed twice.
- Return the existing receipt instead of creating a second charge.
- Add regression coverage for the repeated-submit path before merge.
Autometric review
The linked bug raises regression expectations and checks whether the diff matches the ticket.
Regression coverage missing
Retry-path logic changed, but the pull request does not add a test for repeated submit behavior.
Scope drift detected
The diff also edits billing-email copy that is not described in PAY-1842 or the linked bug notes.
Ticket evidence attached
Repro steps and expected behavior stay attached to the same review record and export path.
Bug-aware review
Linked defects can demand regression coverage before merge.
Intent check
Out-of-scope edits surface as scope drift instead of sliding through unnoticed.
Same evidence path
Ticket context stays attached to the review record and export trail.
Jira + Jira Data Center
Bring linked bug and enhancement context into the same review flow.
GitHub Issues
Reuse the issue system already attached to the code host.
Linear + Monday.com
Keep acceptance criteria and task intent visible while review stays in the SCM.
[what changes]
The review can evaluate the change against intent, not just the diff.
- Bug tickets can demand regression coverage before merge.
- Feature and task tickets can be checked against acceptance criteria.
- Unknown or weak ticket alignment can surface wrong-intent or incomplete work.
- Read-only by design: no ticket creation, no status changes, no workflow sprawl.
[where it fits]
Task Context stays inside the same Autometric flow.
SCMs are still where review lands. Compliance is still where control mapping and evidence attach. Task Context is the bridge that brings linked bug and enhancement details into that same review path.