Skip to main content

Manage Releases and Requirements

This document explains how to use the Plans module in TestOps to plan for releases and manage requirements synced from your ALM tools (such as Jira or Azure DevOps).

Plans Module View
requirements

  • A connected ALM tool:

  • Sprints must have a start and end date, or the sprint may not show up on the timeline.

In the Plans section of TestOps, you can:

  • Track release and sprint schedules from your connected ALM.
  • Create releases in TestOps, as an alternative to ALM releases.
  • View upcoming or ongoing sprints in a visual timeline or structured releases table.
  • Assign testers to requirements directly within TestOps.
  • Create and manage releases with test runs.

Overview of Plans Views​

The Plans module offers two viewing modes:

  • Timeline (default): A visual calendar view showing sprints and releases chronologically.
  • Releases: A structured table view displaying all releases with detailed information including status, test runs, and dates.

Switch between these views using the tabs at the top of the Plans page.

Use the Releases View​

The Releases view provides a comprehensive table of all your releases with the following information:

  • Name: The release name with a pin icon indicating linked releases.
  • Description: Optional details about the release.
  • Status: Current state of the release (e.g., UNRELEASED).
  • No. Test Runs: Number of test runs associated with the release.
  • Start Date: When the release begins.
  • Release Date: Target completion date.

Releases can be filtered by Status and Source.

Plans Module View

Create a TestOps Release​

To create a TestOps release:

  1. Click the Create + button in the top-right corner of the Releases view.
  2. In the Create Release dialog, fill in the following fields:
    • Name (required): Enter the release name.
    • Start Date (optional): Select the start date using the date picker (DD/MM/YYYY format).
    • Release Date (optional): Select the target release date (DD/MM/YYYY format).
    • Description (optional): Add any additional context or details about the release.
  3. Click Create to save the release, or Cancel to discard.

TestOps releases can be filtered out using the Source filter > TestOps, and can be linked to a test run when scheduling/creating a manual test run or automated test run.

Use the Timeline View​

The timeline view puts together all releases created inside TestOps or synced from your ALM tools as a timeline.

Explore the Timeline View with our interactive guide:

  1. If you have multiple ALM tools connected, select the appropriate integration from the Integration dropdown at the top-right of the screen.
  2. Click on any sprint or release to open a drawer displaying all linked requirements.

From here, you can:

  • Assign testers: Click the Tester dropdown to assign a user to a requirement.
  • Filter by tester: Use the Filter Tester feature to view only requirements assigned to you or others.

Explore with our interactive guide:

  1. In Timeline View, click the release to open its requirements list.
  2. Click on a requirement to open the requirement details page. Here you can view the requirement's details to assess and link test cases to it.
    1. Link existing test cases: click Link Test Case, then select one or more from the list.
    2. No suitable test case: click + Create Test Case and fill in the required fields to create one. Assigned

Manage Test Runs in Releases​

Each release can have associated test runs that help track testing progress:

  • View the number of test runs in the No. Test Runs column.
  • Click on a release name to view detailed information about its test runs.
  • Test runs are linked to releases to provide traceability between testing activities and release schedules.

Best Practices​

  • If data feels outdated, click Sync button at the top right corner to re-sync data from your connected ALM tool.
Plans refresh button to re-sync data to ALM tool
  • Regularly update release statuses to reflect current progress.
  • Use the filtering options to focus on specific timeframes or statuses.
  • Assign start and release dates to all releases for better tracking in the Timeline view.
  • Use either TestOps release or release synced from your ALM tool, not both, to avoid overlapping.
  • Leverage the search functionality to quickly locate specific releases.
  • Monitor the test runs count to ensure adequate test coverage for each release.
Was this page helpful?