Tables Filtering Schemes

Boards

PROJECTS (JIRA SOFTWARE) BOARDS BOARDS TYPES

Filtering schema

  1. Loading boards filtered by BOARDS TYPES filter values (by Boards.TYPE). 
    Filtering skipped if BOARDS TYPES filter is not active.

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Export resulted boards list.

Expected result

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list and filtered by BOARDS TYPES.

 

Sprints

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS SPRINTS STATES

Filtering schema

  1. Loading boards with scrum and simple types (Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from step 2 filtered by SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS STATES filter is not active.

  4. Loading sprints by SPRINTS filter values.

  5. Filtering sprints loaded on step 4 by SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS STATES filter is not active.

  6. Export resulted unique sprints list subject to the condition of uniqueness of the natural key (Sprints.SPRINT_ID + Sprints.BOARD_ID).

Expected results

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list filtered by scrum and simple boards types.

All unique sprints loaded by unique boards list and SPRINTS filter values filtered by SPRINTS STATES filter.

 

Board Sprints

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS SPRINTS STATES

Filtering schema

  1. Loading boards with scrum and simple types (by Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from steps 2 filtered by SPRINTS filter values (Sprints.SPRINT_ID) and SPRINTS STATES filter values (Sprints.STATE).
    Filtering skipped if SPRINTS filter and SPRINTS STATES filter are not active.

Expected results

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list filtered by scrum and simple boards types.

All sprints loaded by a unique boards list filtered by SPRINTS and SPRINTS STATES filters.

 

Board Issues

PROJECTS (JIRA SOFTWARE) BOARDS BOARDS TYPES FILTER BY JQL

Filtering schema

  1. Loading boards filtered by BOARDS TYPES filter values.
    Filtering skipped if BOARDS TYPES filter is not active.

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) are not active.

  3. Loading issues by the resulting boards list filtered by FILTER BY JQL value.
    Filtering skipped if FILTER BY JQL is not active.

Expected result

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list and filtered by BOARDS TYPES.

All Issues filtered by boards and FILTER BY JQL value loaded and exported.

 

Issue Sprints

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS SPRINTS STATES FILTER BY JQL

Filtering schema

  1. Loading boards with scrum and simple types (Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from steps 2 filtered by SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS STATES filter is not active.

  4. Loading sprints by SPRINTS filter values.

  5. Filtering sprints loaded on step 4 by SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS STATES filter is not active.

  6. Loading issues by the resulting sprints list filtered by FILTER BY JQL value.
    Filtering skipped if FILTER BY JQL is not active.

Expected result

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list and filtered by scrum and simple boards types.

All unique sprints loaded by unique boards list and SPRINTS filter values filtered by SPRINTS STATES filter.

All sprints issues filtered by FILTER BY JQL value loaded and exported.

 

Sprint Reports

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS SPRINTS STATES

Filtering schema

  1. Loading boards with scrum and simple types (Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from steps 2 filtered by SPRINTS filter values (by Sprints.SPRINT_ID) and SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS filter and SPRINTS STATES filter are not active.

  4. Loading sprints reports data by unique natural key (Sprints.SPRINT_ID + Sprints.BOARD_ID).

Expected results

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list filtered by scrum and simple boards types.

All sprints loaded by a unique boards list filtered by SPRINTS and SPRINTS STATES filter.

All unique sprints reports items loaded and exported by unique Boards.BOARD_ID and Sprints.SPRINT_ID combination.

 

Sprint Report Issues

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS SPRINTS STATES ISSUES TYPES ISSUES STATUSES

Filtering schema

  1. Loading boards with scrum and simple types (Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from steps 2 filtered by SPRINTS filter values (by Sprints.SPRINT_ID) and SPRINTS STATES filter values (by Sprints.STATE).
    Filtering skipped if SPRINTS filter and SPRINTS STATES filter are not active.

  4. Loading sprints reports issues data by unique natural key (Sprints.SPRINT_ID + Sprints.BOARD_ID).

  5. Filtering sprints reports issues data by ISSUES TYPES and ISSUES STATUSES filters values.
    Filtering skipped if ISSUES TYPES and ISSUES STATUSES filters are not active.

Expected results

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list filtered by scrum and simple boards types.

All sprints loaded by a unique boards list filtered by SPRINTS and SPRINTS STATES filter.

All unique sprints reports issues loaded and exported by unique Boards.BOARD_ID and Sprints.SPRINT_ID combination filtered by ISSUES TYPES and ISSUES STATUSES filters values.

 

Velocity Charts

PROJECTS (JIRA SOFTWARE) BOARDS SPRINTS

Filtering schema

  1. Loading boards with scrum and simple types (Boards.TYPE).

  2. Filtering boards by BOARDS filter values (by Boards.BOARD_ID) and PROJECTS (JIRA SOFTWARE) filter values (by Boards.LOCATION_ID).
    Filtering skipped if BOARDS filter and PROJECTS (JIRA SOFTWARE) filter are not active.

  3. Loading sprints by boards ids list from steps 2 filtered by SPRINTS filter values (by Sprints.SPRINT_ID).
    Filtering skipped if SPRINTS filter is not active.

  4. Loading velocity charts data by unique natural key (Sprints.SPRINT_ID + Sprints.BOARD_ID).

Expected results

All unique boards chosen by BOARDS and PROJECTS (JIRA SOFTWARE) filters are combined into one list filtered by scrum and simple boards types.

All sprints loaded by a unique boards list filtered by SPRINTS filter.

All unique velocity charts items loaded and exported.