Modifying or deleting aggregate properties
Navigate to aggregate properties page
- Sign in to Mingle as a project administrator and open the project in which you want to create a card tree (if you're not already working in the project).
From anywhere in Mingle
- From the Project admin menu, select the Card trees link. Mingle will take you to the Card trees page. Then select the Configure link next to the Card tree where you want to create the aggregate property.
Or, from Card Tree view
- Select View tree configuration in the area above the tree.
Select configure in the card configuration that is shown.
Mingle will display the Configure card tree page.
From the Configure card tree page, click on the Edit aggregate properties link. Mingle will display the Aggregate properties page.
Modify an aggregate property
Open the aggregate property control...
Click on the Edit aggregates link on the card type where the aggregate property is defined. Mingle will display the Aggregate properties control, with existing aggregate properties for this level of the tree listed at the bottom.
click on the edit link next to the aggregate property you want to modify. Mingle will populate the control with the current settings for that aggregate property.
Configure the aggregate property...
Enter a new name for the aggregate property
Effects of renaming an aggregate property
- The name will be changed in any card types using the property
- Any MQL which referenced the original property name will display an error, this may affect charts and tables
Select a different aggregation type you want to apply (Sum, Average, Minimum, Maximum, Count).
Aggregate properties ignore values of (not set), so the Average of [1, 3, 6, (not set)] is 3; and the Min of [1, 3, 7, (not set)] is 1;
Select a different scope for the aggregation. You can choose between a specific card type or All descendants.
- A specific card type will apply the aggregation to only descendants of the currently selected level in the tree which are of the specified type.
- All descendants will aggregate the selected property for all descendants regardless of type.
- Define condition... will aggregate the children cards that meet the specified MQL condition. For example, if you want to aggregate stories and bugs but not tasks you can use "Type = Story or Type = Bug and Type != Task" or if you want to aggregate only the Must stories then use a query such as "Type = Story and Priority = Must"
- Select a different property which you want to aggregate from the list of available child properties.
For All descendants - if the property is not present in all descendant card types, the aggregation ignores types which do not declare the property.
Or - Delete an aggregate property...
click on the delete link next to the aggregate property you want to delete.
Consequences of deleting an aggregate property
- The property will be removed from any cards which were using it, and the values will be deleted.
- Favorites that include the deleted property as a display column will be deleted
- Any tabs based on those favorites will also be deleted
- Pages and tables/charts that reference the deleted property will no longer work. The MQL syntax will not be changed, so you will need to manually alter any affected pages to remove references to the deleted property.
A fast way to find all of the pages which use the aggregate property in MQL is to use the Mingle search.
Simply type in the name of the aggregate property e.g. "some aggregate property" and hit the Search
Mingle will show all pages referencing the aggregate property - you can then open each of these pages for editing and make the appropriate changes.
Note that if your aggregate property name is a common word or phrase - you may get some additional pages that contain that word outside of MQL statements.
Save your work...
Click on the to save your changes to the aggregate property
Mingle will display the modified aggregate property in the list at the bottom of the Aggregate property control, or if you deleted the property - it will no longer be displayed there.
To check that the aggregate property is working as you expect, open a card of the appropriate type which is a member of the tree in which you created the aggregate property, and take a look at the value.
Aggregate values are re-computed in the background, so it may take a few moments before your changes are visible.