QA and Test Execution

The Situation

A QA lead has a list of test cases for a feature in a spreadsheet, and needs each one tracked with an owner and a due date.

The Approach

1. Create a story or task for the test cycle.
2. Build the sheet with Summary (test name), Assignee (tester), Priority, and Story Points (effort).
3. Import the sheet as subtasks.

Result

Testers see their cases as subtasks. The lead sees progress on the parent issue. Priority shows which cases to run first.

Tips

• Map any custom field you use for test IDs. Custom fields are available from the project's create metadata.
• Use the preview editor to catch duplicate test names.