Each exported table has its
...
filtering flow, which depends on the activity of various
| Status | ||||
|---|---|---|---|---|
|
| Status | ||
|---|---|---|
|
| Info |
|---|
Filters for the main entities of the exported table |
...
mainly combine the resulting filtered data. Filters for the depended entities mainly filter our data that was collected by the main |
...
entities filters. |
...
Consider the Sprint Report Issues table as an example.
...
In the Sprint Report Issues table, the main entity is the board.
...
The sprint that is associated with
...
this board
...
is a dependent entity.
...
The issue that is associated with
...
this sprint
...
is also a dependent entity.
Thus,
...
If after that we add other filters related to sprints. We will get a result set with less data.
...
If we activate filters by issues, the resulting data set will also be reduced.
...
when you apply filters by
...
Projects and Boards, the resulting filtered data will be combined. You will get all boards linked via JQL to the selected project and the selected board.
If then, you apply filter by Sprints, the resulting filtered data will be reduced.
Remember that the filters for dependent entities filter out the data collected by the main entity filters. In this scenario, if you select sprint that do not belong to any of the boards selected in the filters by Projects or by Boards, the resulting filtered data will be empty.
Thus, each of the exported tables has its
...
filtering flow, which can be used to achieve maximum filtering flexibility.
