Resources for Test Management in Jira
Practical guidance on Jira test management, test cases, release testing, AI-assisted QA, and Sherlock. product updates.
Test Case Approval Workflows in Jira: Roles, Reviews, and Change Control
A refund test case was approved last week. Today, its expected result has changed, but the Jira work item still says Approved. Before the…
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…
Leaving Zephyr in Jira Cloud: Export Test Cases and Results Before Cancellation
A QA team leaving Zephyr needs more than a spreadsheet that opens successfully. It needs the test definitions it intends to keep, the execution…
Import Test Cases From Excel to Jira: Map Steps and Requirement Links
A spreadsheet can arrive in Jira with every row accounted for and still lose the information a tester needs. Actions may become a block…
Load Testing vs Stress Testing: Goals, Metrics, and When to Use Each
A checkout service can meet its response-time targets during a forecast sales peak and still remain unhealthy after an unexpected surge. Requests may accumulate…
Link Existing Jira Bugs to Test Steps: A Zephyr Data Center Guide
A manual test step fails, and the team has already filed the matching Jira bug. The remaining task is to connect that existing issue…
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…
What Is Exploratory Testing? Charters, Session Notes, and Debriefs
A workspace invitation works when a new user follows the expected path. Then the team changes how invitations are revoked. The existing happy-path test…
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…
AI Test Case Generation: A Requirements-to-Review Workflow for QA
A generated case says, “Enter an invalid quantity and verify the correct error.” It has a title, steps, and an expected-result field, yet another…
Risk-Based Testing: How to Score Risks and Prioritize Your Tests
A release changes payment retries, tax calculations, and stock updates. One tester has four hours before the release review. Running the shortest tests first…
Smoke vs Sanity Testing: Key Differences and When to Use Each
A new checkout build reaches the test environment. Before assigning detailed tests, you need to know whether users can sign in, find a product,…
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 Test Execution Explained: Assignments, Statuses, and Blockers
A Jira item marked Done does not, by itself, tell a QA lead whether the checkout tests passed. The testing work may have finished…
7 Test Environment Management Checks to Run Before Test Execution
A regression run fails halfway through checkout. The team can investigate the application, but first it needs to know whether the same build is…
Manual vs Automated Testing: Differences, Costs, and Best-Fit Uses
A checkout change can leave a team with two different jobs: confirm that agreed discount rules still produce the right totals, and investigate whether…
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…
Verify Bug Fixes in Jira: Retest, Reopen, and Close With Evidence
A developer marks a bug fixed, but the test environment may still contain the old build, different feature flags, or data that no longer…
Self-Healing Test Automation: How AI Agents Repair Tests Safely
A checkout test fails after a UI update. An AI agent changes its locator, reruns the test, and returns a passing result. Before accepting…
Test Effort Estimation: Build a QA Forecast With WBS and Three-Point Ranges
A refund change is nearly ready, and the release manager asks whether QA can finish this week. The tester can estimate the first execution…
Test Case vs Test Suite vs Test Run: Differences and Reuse Examples
A password-reset check fails on one build and passes after a fix. If the team changes a single “Status” field from Failed to Passed,…
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…