Decide the scope of your agile board


You can have different agile boards with different scopes. 

  • Track Specification - If you want to track the Test Specification progress, you may have a specific board only with Tests, Pre-Conditions and Test Sets. 
  • Monitor Execution - If you want to track the execution progress, you should include the test execution issues inside your board, along with stories, bugs or other relevant tasks for your project. 
  • Track Requirement Status - if you just want to see the requirement status (uncovered, ok, nok, etc) of your requirements, you just need to add the custom field "Requirement Status" to you Cards. 


It's not recommended to include in the board Test Executions coming from automated testing (i.e. during CI), as it will overload the board and not provide any real added value. Instead, you may include only Test Plan(s) as a means to group and show the consolidated results coming from automation.

Configure filter for the board


At Project Side Bar select Backlog or Active Sprint >  Board > Configure.


Then, choose General and edit the Saved Filter.


Update the query of the saved filter to contain the relevant issues.


In order to make sure that only the relevant issues appear (e.g. Stories, Bugs, Test Plans and not Tests) in the Backlog and in the Active Sprint, you need to configure the filter properly.

The exact filter to use depends on the issue types you have on your project; a possible filter could be:


project = CALC AND issuetype in (Story, Epic,Bug, Task,"Test Plan", "Test Execution", "Sub Test Execution") ORDER BY Rank ASC