Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • Defining Teamspaces
  • Reviews and Surveys
  • Teamspace settings
  • General settings
  • Teamspace members
  • Integration scoping rules
  • Investment mix

Was this helpful?

  1. Features

Teamspaces

PreviousSurvey WorkflowNextInbox

Last updated 1 month ago

Was this helpful?

Reviews and Surveys are organized into Teamspaces.

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:

Reviews

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

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

  • Secondary sort: End date (from newest to oldest)

  • Tertiary sort: Last updated (from newest to oldest)

The most recent Review in a chain must be Published before a new Review can be added to the chain.

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

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.

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.

Teamspace settings

General settings

Change the Teamspace name in General settings.

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.

To add Teamspace members, click Add members

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

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 within a Review, but Teamspace members are a common reason for not seeing the data you might expect in a Review.

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.

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

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.

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 Organization Settings in order to see monetary costs reflected in Investment mix widgets.

Using Jira Automations for complex Investment Mix mappings

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

Primary sort: (Draft, In Progress, Published)

To add a new Review to an existing Review chain, click Repeat on any Review chain:

To create a brand new Review chain, click New Review and select from the available .

To access Teamspace settings, click the ellipsis to the right of the Teamspace name in the left-hand navigation:

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

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 .

Review templates
Investment mix settings
Jira Automations
Investment mix settings
Review state
Emojis highly recommended 😆