Cross Project Reporting

Introduction

Cross project reporting allows you to report on multiple Mingle projects on a single Mingle project wiki page or card. For data series and stack bar charts you can also report on multiple projects on a single chart. This allows you to access data from multiple Mingle projects at once and see the data in a single cohesive view.

Two projects reporting on the same page - 1

Two projects reporting on the same page - 2

This feature is particularly useful for large programs of work where you can view individual projects summaries in the context of other projects within the same program.

To create cross project reports like these use the macro's "project" parameter at the chart or the series level. Review the macro reference for more information.

The daily history chart does not support the use of the project parameter and therefore, cannot be used to create cross project reports.

Cross project macros

Mingle 3.0 includes updates to the Macro Development Toolkit to facilitate cross project reporting for program management. As an example of the cross project macro functionality available via the Macro Development Toolkit, Mingle 3.0 ships with a new macro called cross-project-rollup.

Cross project rollup

This macro does not appear in the Macro Editor. To use this macro, use the markup example below as a template for your own cross project reports.

A macro that aggregates property values across multiple projects. This macro only works with Mingle 3.0. The cross-project-rollup macro will work using the following markup:

{{
   cross-project-rollup
   project-group:  project_3_0_features_showcase, another_project_in_my_program
   rows: Feature
   rows-conditions: Feature != NULL
   columns:
   -     label: Number of stories
         aggregate: count(*)
         conditions: type = story
   -     label: Number of Must stories
         aggregate: count(*)
         conditions: priority = must and type = story
   -     label: Estimate of Must stories
         aggregate: sum(estimate)
         conditions:  priority = must and type = story
   total: true
}}

Preview

The following is a list of parameters and how they should be used with this macro:

Parameters
Chart-level options
Name	Meaning	Required	Default value
project-group	List of project identifiers	No	Current project
rows	A property. Each row is a property value. The order of the rows' property values is alphabetical by card name if a card or tree relationship property, by number if they are numeric properties, by display name and login if they are team properties, by date if they are date properties, by the bespoke order of the first project if they are text properties.	Yes
rows-conditions	MQL condition to restrict the rows shown in the table.	No
zero-value-rows	True or false. Determines whether rows with no value will be shown or not.	No	True
columns	Can have many columns. Shown in the order given in the macro markup.	Yes
Column-level options
Name	Meaning	Required	Default value
label	Label for the column. Label will default to the column aggregate if not specified.	No	Column aggregate
aggregate	Can be Count, Sum(property), Min, Max. Cannot be average. Date properties cannot be aggregated.	Yes
conditions	MQL condition to restrict the column aggregation.	No
Other options
Name	Meaning	Required	Default value
total	True or false. Sums the column and shown as row if true. Always shown as the bottom row.	No	True
sub-totals	Only applicable when the column aggregation is count or sum. Calculates a sum of the rows in the column restricted by the subtotal condition. Can have many subtotals. Shown in order given in macro markup.	No
Sub-total options
Name	Meaning	Required	Default value
conditions	MQL condition.	No	Sum total of the column
label	Label for the sub-totals. Label will default to the condition of the subtotal if not specified.	No	Conditions or, if no conditions, empty

Help documentation