Test Plan

Test Plan is a specyfic TestFLO's issue type which agragates Test Case in a Test Cases panel. Thanks to this type, you can plan which test cases you want to perform as part of a given Test Plan and design the order of tests execution. Test Plan can also become a different issue type. To learn how to configure, see Test Execution tab.


Test Plan has several dedicated operations that are available from 'More' menu:

  • Copy Test Plan
    It is very handful to copy Test Plan with selected Test Cases when you do regression test, execute another test cycle or share same test plan with other testers (eg. customers for UAT).
  • Update Test Cases
    It allows to refresh attributes and steps of Test Plan's Test Cases just to make sure there are up to date and testers will do correct actions. Test Cases can be updated also from Test Case Template issue.
  • Create Test Cases
    That is another way of adding new Test Cases into your plan. The dialog window will show up with Test Case Templates list.
  • Assign Test Cases
    It is an easy way to assign all Test Cases to the tester. Just select the JIRA user from drop-down menu and press Assign.


Test Plan can be connected with Requirements using dedicated custom field. That allows you to see Test Progress on Requirements and later Create Defect under Test Case.


You can track progress of test plan execution using dedicated custom field. Progress can be based on Test Cases number or estimation custom field (see Progress CF Based on Number CF). Estimations can be derived from Test Cases (Real Estimated TC Workload & Sum Subtasks Customfield Value).

TP Progress can be shown in filter results or on dashboard (for more examples see TP Reporting).


Aggregate Defects from all TCs in your plan. Show them in filter results or on dashboard. Resolved defects are strikethrough.


Workflow can be customized including statuses, conditions, validators and post-functions.

For example you can decide that:

  • Test Plan cannot be completed until Test Cases are resolved (pass/fail). See Subtasks Status condition for more.
  • Test Plan cannot be started until all technical tasks are resolved that prepare test environment (use Subtasks Status condition with conjunction with Technical sub-task issue type).
  • Make snapshot of test progress state when Test Plan goes to given status (i.e. Acceptance, Resolved, Closed).
  • Reopen TCs when Test Plan goes to retest. You can reopen not executed TCs or all of them. (Use Subtasks Transition post-function to accomplish that scenario.)
  • Run automated tests and...
  • ...use any other condition, validator, post-function you have in your JIRA to adjust your Test Plan workflow.


You can use JIRA Time Tracking feature to estimate and log work on tests. Because TC is a subtask of Test Plan, you can see overall estimates of tests on Test Plan level.


List all your Test Cases under Test Plan. Show custom columns to reflect all information you want to be visible on plan (eg. Defects, Assignee/Tester, Status, Steps Progress, Environment, etc.). You can change order of Test Cases in Test Cases panel using Drag&drop option or use the up&down arrows. You can decide how many Test Cases are visible on panel (see Test Case section for more information about pages).

User can decide whether the Test Case panel should be in the default or extended view.


If you enable Expanded view on other issues such as Test Case and Test Case Template, it will also work for the Test Plan.


Test Cases can be also grouped under Test Plan for better transparency and logical structure.

  1. Use Add Test Case Group to add specific group for Test Cases.
  2. Use cog icon to move selected Test Cases to given group.
  3. Use arrows to change the order of Test Case group.
  4. Click Show in issue navigator link to redirect to Issue Navigator. From that point you can execute bulk change on group of your test cases:
  • Change assignee (issue edit)
  • Pass/Fail/Retest many tests at once (issue transition)
  • Change version, component, due date, etc. (issue edit)


Test Plans can be executed many times producing different results. Snapshots allow to save TP state at given time.

You can use snapshots for:

  • regression tests
  • tests for different builds
  • tests for different environments
  • etc.

It is possible to save in snapshot:

  • Date & time when snapshot was created
  • List of TCs
  • Status, summary, key of each Test Case
  • Who executed each Test Case
  • Reported defects
  • Connected Requirement
  • Test Result
  • Custom field from Test Plan like TP Progress, etc.