Page History
...
The following picture depicts the several key areas of the Test Plan Board screen, which includes the Board itself along with some other auxiliary folders.
- T: Title section
- T1: Test Plan's issue key (with the possibility of switching to another issue)
- T2: Test Plan's Overall Execution Status
- A: Folders section
- A1: "All" and "Orphans" metafolders
- A2: the Test Repository itself, composed of folders and sub-folders with Tests organized within them
- A3: CRUD actions for the current selected folder (e.g. create, rename, delte)
- A4: information about the the amount of Tests within in the current folder and the total Tests, including sub-folders
- B: Tests section
- B1: path of the folder
- B2: overall execution status for this folder (takes into account the Test Environment selected)
- B3: Test Environment to consider for the calculation of the overall execution status for
- B4: filter for Tests
- B5: additional information about the shown Tests vs the actual total amount of Tests within the current folder
- B6: ranked list of Tests within the current folder (only direct childs)
- B7: calculated status for each Test, on the selected Test Environment
Clicking on T1 will jump into the standard Test Plan issue screen.
...
By allowing you to see the progress per folder (B2), you're able to analyze the status of some subset of Tests that are in part of the Test Plan.
The analysis per folder 
folder takes into account the selected Test Environment; by default it shows the calculated status for "All Environments".
The values shown per each folder only take into account the immediate child Tests (i.e. the Tests that are within that folder). Thus, this bar shows the totals for the Tests that are seen "underneath" it.
On the right side of each Test (B7) you will be able to see the current calculated status for that Test, in the context of the Test Plan and the selected Test Environment. The shown status corresponds to the last run made for that Test in the scope of the related Test Executions, taking into account the selected Test Environment.
Analysis by Test Environment
Tests can be analyzed per Test Environment (i.e. taking into account the results for some given Test Environment) using the proper action (B3), so you can see the current testing status for that environment.
Thus, you're able to analyze on a per Test Environment basis or see the overall status, if you choose "All Environments". For more information on using Test Environments and the calculation of the status for a given environment, please see Working with Test Environments.You can analyze the status of the Tests in the context of the Test Plan for each Board's folder; thus, you have a more finer control over the actual status of some subsets of the Tests.
The analysis by Test Environment is only applicable to the folder progress bar (B2).
| Info | ||
|---|---|---|
| ||
If you want to evaluate the overall status of your Test Plan for some Test Environment, you can do it in the "All" meta-folder. |
Folder Actions
A folder can be selected by clicking on it.
...
This action in fact corresponds on "moving" them from any folder they may already be in (including the Orphans) to the destination folder. Thus, if you "add" a Test that currently is in some folder within the Board, to some destination folder, then it will be moved from the source folder to the destination folder.
Note that Tests must already be part of the Test Plan. If you with to add Tests to the Test Plan, then you need to go to the Test Plan issue screen and use the "Add Tests" button there.
In order to "add" Tests to a folder,:
Step 1: Click on the folder
...
Step 3: Choose the Tests you want using the provided filters, a previously saved filter or by JQL
Note: if you try to add non Test issues or Tests that are not part of the Test Plan (e.g. by using a saved filter), an error will be shown.
...