Important notice to CircleCI customers!

As per this security alert posted on January 4th, CircleCI has invalidated all personal API tokens.

Impact on your Sleuth Implementation:
This means that any CircleCI-related Sleuth integrations such as build detection, build impact detection, or custom Sleuth actions have been broken since CircleCI invalidated these tokens.

Solution:
We recommend that all Sleuth customers using CircleCI immediately:
  1. Rotate your personal tokens in CircleCI (see CircleCI help doc)
  2. Disable any existing CircleCI integrations from within Sleuth (see Sleuth help doc)
  3. Add new CircleCI connections in Sleuth using your newly generated CircleCI tokens (see Sleuth help doc)
While CircleCI’s incident has had no security-related impact on Sleuth nor on the data you share with us, we recognize and apologize for the inconvenience and are here to support you through any questions or concerns.

Sleuth Team

Announcing Work in Progress 2.0!

Following on our December release of Work in Progress, we've added even more features to make this dashboard even better!

This latest release includes:

  1. The ability to subscribe to work in progress email digests 
  2. The ability to filter and sort the work in progress listing by specific risk types
  3. A slew of UI/UX improvements to bring your focus to what matters most

Check out the updated help doc and blog post for more info, and be sure to register for the Jan 19 webinar where we'll be talking to Torsten Sinnemann, Engineering Manager at Article, about why he loves Work in Progress for Sleuth!

Announcing Work-in-Progress Metrics!

Sleuth’s Product Team is pleased to announce an exciting new feature that provides early and actionable visibility into emerging work-in-progress risk!

With this release, Sleuth extends its industry-leading, deploy-centric metrics capability upstream in your developer workflow by providing Work in Progress dashboards for Teams and Projects. These new dashboards provide real-time visibility into in-flight work (i.e. work that has not yet deployed) and highlights emerging efficiency risks that you can address right now.

For additional information, check out our recent blog post and the new Work in Progress help doc!

Let Sleuth Actions automatically update your Issues!

Sleuth Actions now provides the ability to transition issue status or add comments to linked Jira and Linear issues!

This feature is particularly useful for notifying product managers, support, and other customer-facing stakeholders when new features, bug-fixes, and other customer-impacting changes have deployed to specific environments.

Check out the Sleuth Actions Cookbook for more examples!  

Announcing Issue-Initiated CLT!

You can now start your CLT clock based on state changes in your issue tracker!

By expanding your CLT lens to include your issue tracking workflow, issue-initiated CLT helps you identify and remediate pre-commit bottlenecks and their impacts to your overall coding time.

Check out this blog post for an in-depth discussion on why you might want to enable this new option, and if you decide it might be the right choice for your team, check out this help doc for instructions on how to enable and configure it for one or more of your Sleuth projects!  


Environment support is here!

If you have been representing environments with multiple projects in Sleuth, fret no more: Sleuth now offers first-class environment support, and we couldn't be more excited! Be sure to watch CTO Don Brown's awesome video and read his blog post on Sleuth's new first-class Environment support!

Environment settings
 
Sleuth's environment support allows you to track changes across environments within a project to understand what state each environment is in, and also to know when and what changes are shipping to production. Switching between environments is as easy as switching between projects, using the selector shown above. 

Existing users don't need to do anything. After logging in, you will see both a Production and Staging environment in your Sleuth projects, with the Production environment set as the default. You can change this and other settings (for example, a master branch mapped to Production, a different branch mapped to Staging, etc.) to accommodate your development workflow.

Read more about Sleuth Environment Support and how to configure Environments in your Project Settings

Happy deploying!

Updated pricing scheme

Our FREE and STANDARD plans both provide up to 50 deploys per month, with 25 additional deploys at only US$25. We can also tailor a CUSTOM plan for you if those don’t work for you. 

For more information, visit our updated Pricing page. You’re sure to find a plan that works for you and your team.