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
  • Survey Recipients
  • Survey States
  • Adding survey results to a Sleuth review
  • Sharing surveys

Was this helpful?

  1. Features
  2. Surveys

Survey Workflow

PreviousSurveysNextTeamspaces

Last updated 1 month ago

Was this helpful?

All Surveys follow the same workflow:

  • Create a list of Survey questions

  • Send out survey to all recipients

  • Collect responses

  • Review and comment on summarized findings

  • Share completed Survey results (either directly or by adding them to a Review)

Survey Recipients

Each survey includes a list of Survey recipients - a list of named users or teams that will receive the Survey questions. Recipients can include any PR or issue contributors even if they aren't Sleuth users. See Users and Teams for more information.

Once the Survey moves from Draft to In Progress, each recipient receives the survey in Slack and can also respond to it there (without logging into Sleuth).

Survey States

All Sleuth Surveys move through the following three states:

  • Draft: This is the initial state where Survey Owners and collaborators can work together to create a list of questions to be answered by the Survey recipients. Once the Survey Owner is satisfied with the list of questions, they can send the survey to all recipients by clicking the Start survey button.

  • In progress: When the Survey transitions into this state, all recipients receive the list of Survey questions to answer in Slack. As recipients complete their answers, questions are updated and summarized in Sleuth using quantitative visualizations and narrative summaries generated by Sleuth's . Once a Survey owner determines that they have enough responses, they Publish the survey by clicking the End survey button, moving the Survey to its final state.

  • Published: Sleuth "freezes" Surveys once they are published in order to preserve their history. Survey Widgets stop updating, even if additional responses are provided, and users are no longer able to edit the content of the Survey. If needed, Survey owners and Sleuth admins can manually revert a Survey to In Progress by selecting Unpublish survey from the Survey menu that appears when clicking on the ellipses at the top of the Survey.

Adding survey results to a Sleuth review

Final Survey Results can be added to any Review in Sleuth using the Survey Results Widgets.

From any Review, insert the Survey Result Widget, then configure the widget by selecting the Teamspace where the Survey resides and the specific Survey within that Teamspace that you want to include.

Once the Survey has been selected, Survey results will automatically display in the Review.

Sharing surveys

Once published, Survey owners can share Surveys by sending them as a link, downloading them as a PDF, or using Presentation mode to show the Survey results and questions as a slide presentation right within Sleuth.

AI Assistant