Resources for Test Management in Jira
Practical guidance on Jira test management, test cases, release testing, AI-assisted QA, and Sherlock. product updates.
Trigger GitLab Tests From Jira Cloud: Set Up On-Demand QA Runs
A tester reviewing a Jira issue may need a fresh smoke run without opening GitLab and choosing pipeline parameters. A manually triggered Jira Cloud…
Jira Cloud Automation Limits for QA: Diagnose Throttling vs Monthly Caps
A scheduled QA flow stops updating release-readiness notes. Some work items may already have changed, others may still be waiting, and the last visible…
QA Capacity Planning in Jira: Match Sprint Scope to Team Availability
A sprint can contain carefully estimated testing work and still overload the only person who can perform it. The missing input may be a…
Jira API Rate Limits for QA Integrations: Handle 429s With Safe Retries
A regression-results worker receives HTTP 429 while reading Jira issues. Sleeping that worker may be necessary, but it will not help if other workers…
7 Jira QA Dashboard Gadgets for Bugs, Blockers, and Testing Progress
A release review can show fewer open bugs while regression testing is still incomplete. Developers may have resolved defects that testers have not yet…
QA Community of Practice in Confluence: Charter, Sessions, and Knowledge
When testers on different teams keep asking how to investigate timeouts or explain uncertain results, another delivery-status meeting will not preserve the learning. A…
Defect Leakage in Jira: Measure Escaped Bugs Without Skewing Rates
A production-bug filter can return the right tickets and still produce the wrong defect leakage rate. If the denominator excludes defects fixed during testing,…
Defect Triage in Jira: Set Severity, Priority, Owners, and Next Steps
A Jira backlog can contain several High-priority bugs while leaving the team unable to answer a basic question: what should happen next? One report…
Restrict Sensitive Bugs in Jira Cloud With Issue Security Levels
A defect report can belong in a shared Jira project without belonging in every project member’s view. An ordinary bug may need broad triage,…
Jira Automation for QA: Send Stale-Bug Reminders Without Email Spam
A QA lead wants owners to review neglected bugs before the weekly backlog meeting. A scheduled Jira rule finds the right issues, but sends…
AI Test Cases From Confluence: Generate, Review, and Link Them to Jira
A generated refund case can cite the correct Confluence page and still omit the permission check that prevents an unauthorized refund. It can also…
Bug vs Incident in Jira: Separate Service Recovery From Defect Fixes
A development team can finish a bug fix while customers still cannot use the service. A response team can restore service while the underlying…
Rovo for QA in Jira: Where AI Helps and Human Review Still Matters
A Jira story changes its acceptance criteria after regression planning has started. A QA lead asks Rovo to identify affected tests and suggest missing…
Jira AI Data Privacy for QA: Permissions, Retention, and Data Contribution
A bug report can contain everything needed to reproduce a failure and several things nobody intended to send to an AI service: a customer…
Jira Incoming Webhooks for QA: Authenticate and Verify CI Callbacks
A CI job can receive HTTP 200 from Jira Cloud while the intended automation rule never runs. Atlassian documents this behavior for the post-May…
Jira Bug Bash: Plan Team Sessions and Track Findings With Labels
A checkout problem arrives as a screenshot in chat. A designer notices confusing delivery options, while a support colleague records a different symptom in…
Playwright Jira Integration: Send Test Results Through Xray and CI
A Playwright job can produce a valid JUnit XML file while Jira shows no new test results. The report may never have been uploaded,…
Jira QA Automation: Prevent Duplicate Tasks and Rule Loops in Cloud
A story enters Ready for QA and Jira creates a testing subtask. After rework, the story enters the same status again and receives another…
5 Cross-Team QA Dependency Checks in Jira: Blockers, Links, and Owners
Checkout testing is waiting for a payment-service change. The payment work item says Done, the checkout work item has a link, and neither team…
Jira Audit Log vs Issue History: What Each Proves for QA Reviews
A refund work item has moved to Done, but a reviewer suspects that its workflow changed before testing finished. Which record should the QA…
Xray Migration to Jira Cloud: Validate Test Data Before Cutover
A Jira project opens in Cloud, its Test issues are visible, and the migration dashboard shows success. Before reopening testing, the QA lead still…
Cross-Project Test Case Reuse in Jira: Xray Cloud Setup and Limits
A shared payment flow can appear in several Jira projects, but copying its test into each project creates separate maintenance work. When the declined-card…
Duplicate Bugs in Jira: What They Are and How to Preserve Evidence
A tester reports a failed checkout, support files a similar customer complaint, and another team records a timeout in the same flow. Treating them…
Create Jira Bugs From Failed Tests: Evidence, Filters, and Review Gates
A checkout test fails, the next scheduled run fails again, and Jira receives another bug with the same unhelpful description. Meanwhile, the original failure…