Investment mix

The Investment mix tab allows you to define rules that "map" your Jira issues into meaningful categories for understanding where developer time and salary are being spent.

These settings are required for any of the "Investment mix..." widgets included in the Investment Mix Review template:

Sleuth lets you define category mapping rules based on common Jira fields. To add or modify a mapping rule for any Investment mix category, perform the following steps:

1. Click Edit for the category you wish to define:

   
2. Specify conditions for the mapping rule using any combination of the available filters, then click Save settings:

   

If Investment mix settings have not been specified for a Teamspace, then Reviews created in that Teamspace will default to the org-level Teamspace's Investment mix settings.

For planned vs unplanned work, both the “Planned” and “Unplanned” categories must be defined

You'll need to specify an average developer salary in order to see monetary costs reflected in Investment mix widgets.

Using Jira Automations for complex Investment Mix mappings

If your logic for mapping Jira issues into investment mix can't be captured using Sleuth's Investment mix settings alone, then we recommend using Jira Automations to pre-label your issues before they come into Sleuth.

Jira Automations allow you define complex conditions using any combination of Jira metadata fields and even supports custom JQL expressions:

By using Jira Automations to pre-label your issues, you can automate complex issue categorization logic in Jira and then simply capture the 1-to-1 mappings between your Jira labels and Sleuth's investment mix categories in Sleuth's Investment mix settings.