View environment drift details right from Sleuth!

Sleuth now provides detailed visibility into the specific deploys, PRs, commits, and issues that comprise the drift between any two environments!

Minimizing drift contributes positively to all four DORA metrics. With this latest improvement, Sleuth now not only quantifies drift in terms of deploys and time but also shows the specific changes that need to be resolved in order to bring two environments in sync. For more information, check out this help doc!

Global Navigation Revamp 🧭

That's right, we've reimagined Sleuth's global navigation experience to make finding what you're looking for a breeze 🏝

This update includes:

  • A new top-level global navigation bar for accessing any organization-wide views (like Organization Settings, User Settings, Search, and the org-wide Status, Trends, and Compare dashboards)
  • A new context picker for bringing a particular Project or Team into focus
  • A context-sensitive left-hand-navigation pane for browsing items that are specific to your selected Project or Team (displayed only when you have one in focus)
  • A number of usability and scalability enhancements, like the new type-ahead search for selecting Projects, Teams, Code Deployments, and Impact Sources

Check out this help doc for more information.

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!

Move code deployments across projects!

We get it, things change. Fortunately, Sleuth now provides the ability to easily move code deployments across projects while maintaining their full deploy history and impact on project-level DORA metrics!

For more information, check out this 
help doc.  

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!  


Show Previous EntriesShow Previous Entries