# Teamspaces

Reviews and Surveys are organized into **Teamspaces**. 

![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FVr5uOq7UlNVLPZPTq9s1%2FCleanShot%202024-12-09%20at%2011.13.22%402x.png?alt=media\&token=8bf8dd5c-9fa3-4780-b048-31d0cfca7bf7) 

Sleuth presents Teamspaces alphabetically in the left-hand navigation pane. All Sleuth users can create Teamspaces, and all Teamspaces are accessible by all Sleuth users

### Defining Teamspaces

Users can define Teamspaces in whatever way best suits their use case. A Teamspace might represent:

* A software engineering team (developers and a Team Lead)
* A "product team" or "scrum team" (including scrum masters, design, PM, QA...)
* A team of teams ("tribes" or "guilds" )
* Supporting teams (SRE, DevEx, Technical Project Management, etc.)
* A single user's "personal" teamspace 

As these examples illustrate, a Teamspace can represent any level in your organization structure. We recommend creating a separate Teamspaces for any group of users that will be performing the same Reviews and Surveys together over time.

### Reviews and Surveys

Each Teamspace has tabs for managing the Reviews and Surveys within the Teamspace:

![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FlVElQqflCLXAPZcjEqYO%2FCleanShot%202024-12-09%20at%2011.14.29%402x.png?alt=media\&token=c3712a85-e09a-48ef-819c-acf9d7606ad7) 

#### Reviews

Reviews are displayed as tiles that each represent a linear "chain" of Reviews created over time:

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FrDS8mE8pIYIAyJ0Rc4FJ%2FCleanShot%202024-12-09%20at%2011.41.57%402x.png?alt=media&#x26;token=fba50d59-bcc3-4f2f-be7c-1cd00b8b296f" alt=""><figcaption></figcaption></figure>

Review chains are sorted based on the most recent Review in the chain as follows:

* **Primary sort:** [Review state](https://help.sleuth.io/reviews/review-workflow#review-states) (Draft, In Progress, Published)
* **Secondary sort:** End date (from newest to oldest)
* **Tertiary sort:** Last updated (from newest to oldest)

To add a new Review to an existing Review chain, click **Repeat** on any Review chain:![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FHGnBlF6yqJ5HrnlgdYCU%2FCleanShot%202024-12-09%20at%2011.48.20%402x.png?alt=media\&token=8db1390d-adf6-4811-941e-58cfc8baa727)

{% hint style="info" %}
The most recent Review in a chain must be Published before a new Review can be added to the chain.&#x20;
{% endhint %}

To view earlier Reviews in a Review chain, click **History:**

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2F34Dtj2uCuTQoOLjkld8D%2Fimage.png?alt=media&#x26;token=cdc8f59a-7186-4ccd-aed7-f6f34b640894" alt=""><figcaption></figcaption></figure>

To "fork" a new Review chain from an existing Review, click **Copy review** next to any Review in the History screen. A new Review chain will be created with the same configuration as the copied Review.

To create a brand new Review chain, click **New Review** and select from the available [Review templates](https://help.sleuth.io/features/reviews/review-templates).&#x20;

#### Surveys

The Surveys tab behaves similar to the Review tab. Surveys are displayed using similar sorting criteria, and the **Repeat**, **History**, and **Copy** actions behave as described above.&#x20;

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2F9tvLIHJeXMRhId00ZUhZ%2FCleanShot%202024-12-09%20at%2012.03.56%402x.png?alt=media&#x26;token=faf6ba02-6a90-480b-a52b-c579500e7fb1" alt=""><figcaption></figcaption></figure>

## Teamspace settings

To access Teamspace settings, click the ellipsis to the right of the Teamspace name in the left-hand navigation:\
![](https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FTX1BOHvp2jkzJ94U9lzJ%2FCleanShot%202024-11-12%20at%2018.18.40%402x.png?alt=media\&token=4f82419f-11de-441b-8c22-d2e76a879db0)

### General settings

Change the Teamspace name in General settings.&#x20;

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FoRQSfJ2OGjsGV9zAyoPi%2FCleanShot%202024-11-12%20at%2018.21.05%402x.png?alt=media&#x26;token=c73fd9d5-f789-45ca-9812-762dee195500" alt=""><figcaption><p>Emojis highly recommended 😆</p></figcaption></figure>

### Teamspace members

You'll be prompted to add Teamspace members when you create a new Teamspace, and you can view and modify Teamspace members at any time by navigating to the **Members** tab in **Teamspace settings**.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2F2gKOnUBGT2h6eH9gqSRa%2FCleanShot%202024-11-12%20at%2018.30.47%402x.png?alt=media&#x26;token=d40cbd80-ecd1-4244-a8ce-b21383c06c15" alt=""><figcaption></figcaption></figure>

To add Teamspace members, click **Add members**

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FjDYrr8ppZQeiu22mPOiC%2FCleanShot%202024-11-12%20at%2018.37.19%402x.png?alt=media&#x26;token=88d78b2c-f8aa-47d6-bd57-638d82de6615" alt=""><figcaption></figcaption></figure>

Sleuth presents all of contributing user and teams that it detects in your integrated tools (PR authors and reviews from GitHub, issue assignees from Jira, etc.). Members that you select here are used to *filter* Review data, not to determine which Sleuth users have *access* to the Teamspace (all Sleuth users have access to all Teamspaces). &#x20;

{% hint style="danger" %}
The people and teams you add as Teamspace members will act as **default filters** for all Reviews created in the Teamspace. You can [override this filter for any Widget](https://help.sleuth.io/features/broken-reference) within a Review, but Teamspace members are a common reason for not seeing the data you might expect in a Review.
{% endhint %}

### Integration scoping rules

Integration rules allow you to limit which Jira projects that are considered "in scope" for the Reviews in a Teamspace.

Setting integration rules improves user experience by automatically filtering out irrelevant issue data and also reduces the loading time for Review data.

To set integration rules, navigate to the **Integrations** tab in Teamspace settings and click **Set rules**.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fa7OD6xhzQ5pdPNtqbR9H%2FCleanShot%202024-11-20%20at%2009.48.13%402x.png?alt=media&#x26;token=e970d92e-6dd2-4642-8d84-b82a1ee8ec70" alt=""><figcaption></figcaption></figure>

Use the **Projects** drop-down to select which Jira projects to include in the Teamspace, then click **Save rules**.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2F9geesOB8VlfoUSXArIXr%2FCleanShot%202024-11-20%20at%2009.53.39%402x.png?alt=media&#x26;token=308bbb9f-e2a6-4878-a15a-394cdee65511" alt=""><figcaption></figcaption></figure>

### Investment mix

**Investment mix** settings allow you to define rules that "map" your Jira issues into meaningful categories for understanding where developer time and salary are being spent.&#x20;

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:

   <figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fxcc33Skxz20yXoO47tlq%2FCleanShot%202024-11-20%20at%2011.26.01%402x.png?alt=media&#x26;token=dcee84b3-c33e-406c-9858-8660fd233c71" 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 [Organization Settings](https://help.sleuth.io/features/broken-reference) 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/investment-mix) 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](https://help.sleuth.io/features/general-settings/investment-mix).