Report Issue Source Configuration

The Issue Source configuration panel lets you specify the issues needed to create your report. As StatusReports can roll up dates from multiple levels of the issue hierarchy, you often want to load a set of issues and their children.

Form Controls

The following explains the different sections of the Issue Source configuration panel:

Open

Primary JQL

The primary JQL is used to load the issues you want to report on. This is a JQL statement exactly like those you might build in Jira’s filters. Often, if the query is complex, you might author the query as a filter, and then cut and paste it here.

Here are some example queries you might use:

• Load all epics for the ecom project:

  type = Epic and project = ecom

• Load all in-progress epics for the ecom project:

  type = Epic and project = ecom and statusCategory = "In Progress"

• Load all initiatives for a particular release:

  type = Initiative and fixVersion in (ENGAGEMENT_R3)

• Load all children of an issue and the issue (KEY-123) itself

  issue in portfolioChildIssuesOf("KEY-123") or issue = KEY-123

Load Children Checkbox

The “Load all children of JQL specified issues” checkbox will tell StatusReports to also load all children for each issue loaded by the Primary JQL. It will continue loading children of those children until there are no more children to load.

This is very useful when you want to report on parent issue types that don’t have dates themselves, but instead, their children have the dates you want to use to calculate the dates of the parent issue type.

For example, Initiatives are often used as a parent issue type of Epics, but it’s common for dates to only be put on Epics and Stories. In this case, you might want a Primary JQL that loads the Initiatives you want to report on (type = Initiative and project = ecom) and to check the Load Children checkbox to load all the child Epics and Stories of the Initiatives.

Children JQL

Sometimes, you only want to load particular children of the Primary JQL. If this is the case, you can add a children JQL filter to limit what issues are retrieved.

For example, suppose you want load in-progress Initiatives and only their child Epics that haven’t been Canceled. You can do this as follows:

• Primary JQL

• Children JQL

Exclude Statuses

Exclude Statuses allows you to exclude statuses from all issue types loaded by StatusReports. This is most commonly used to ignore certain statuses that should never be used to calculate dates. For example, many workflows include a Canceled or Won’t Fix status. Exclude Statuses can be used to ignore those statuses.