# 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.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FWHB5NAEDSI2vqkTIDWEn%2Fimage.png?alt=media&#x26;token=41704e4b-6a6c-4d93-967e-3bf51b407922" alt=""><figcaption></figcaption></figure>

These settings are required for any of the **"**&#x49;nvestment mix..." widgets included in the **Investment Mix** Review template:

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FIobiUSU7n6LYHmcEEnxZ%2FCleanShot%202024-11-20%20at%2010.09.21%402x.png?alt=media&#x26;token=70a41022-526c-46e3-9f55-3dece083ec9f" alt=""><figcaption></figcaption></figure>

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:<br>

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2F5oMyoLsgTrYn58MIe8sP%2FCleanShot%202025-02-07%20at%2010.05.01%402x.png?alt=media&#x26;token=6ba27b9b-6a90-4d9a-91d0-adac283f54c0" alt=""><figcaption></figcaption></figure>
2. Specify conditions for the mapping rule using any combination of the available filters, then click **Save settings**:

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FTreKzC1aAUnEsnJXlGKu%2FCleanShot%202024-11-20%20at%2011.27.49%402x.png?alt=media&#x26;token=0e32120f-8fe0-4f20-a89c-dbeb12decea0" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
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.
{% endhint %}

{% hint style="warning" %}
For planned vs unplanned work, both the “Planned” and “Unplanned” categories must be defined
{% endhint %}

{% hint style="warning" %}
You'll need to specify an average developer salary in order to see monetary costs reflected in Investment mix widgets.
{% endhint %}

#### 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](https://help.sleuth.io/features/general-settings/broken-reference) alone, then we recommend using [Jira Automations](https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation) to pre-label your issues before they come into Sleuth.&#x20;

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

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FXK4itlFYDQf3MWLEq6G1%2Fimage.png?alt=media&#x26;token=b6c713de-03f9-4595-a1b1-e621113ce6be" alt=""><figcaption></figcaption></figure>

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.