/
Report Timing Configuration

Report Timing Configuration

Owned by Justin Meyer
Last updated: Feb 18, 2025 by Benn Lynch
2 min read

Report Timing Configuration is used to specify how data should be calculated across parent and children issues. This configuration is used to rollup dates and for calculating percent complete.

 

For example, let’s say an epic’s dates are set one month apart, but its stories span 2 months. How should we represent that epic’s timing?

image-20250206-163122.png
An epic with dates that don’t encompass its children's stories.

 

The Report Timing Configuration lets you specify how values should be handled between each level of the issue hierarchy. The default configuration will be to take the largest date range across all issue types. This configuration is shown below (for a hierarchy that spans from Outcome to Story):

image-20250211-024512.png

 

However, if you want to report only the epic dates, the following would configure the report to only use dates on Epics and ignore everything else:

image-20250211-025511.png

Options

The following options are available between each type of the issue hierarchy.

  • ↑ From PARENT - Ignore the child type values and only use parent type values.

  • ↓ From CHILDREN - Ignore the parent type values and only use the child type values.

  • ↕ From PARENT or CHILDREN (earliest to latest) - Takes the larger value or date range from the parent or the children. This is the default behavior.

  • ↑↓ From PARENT, then CHILDREN - If there is a parent value, use that value; otherwise, use children’s values.

  • ↓↑ From CHILDREN, then PARENT - If there is a child value, use that value; otherwise, use the parent value.

 

Technical Implementation

StatusReports builds a tree structure of issues. The choices of the options above specify how it rolls up data. Processing data always starts from the bottom of the issue hierarchy. If an option like ↓↑ From CHILDREN, then PARENT is selected, it will check if it can build a value from the children; if it can’t, it then look for a parent value. If a value is produced, the value will then be used as a child value in the next calculation on the next level of the hierarchy.

 

 

 

 

 

Related content