Ignore weekends and "off hours"

Sleuth can now ignore weekends and other hours when teams aren't working.

Customers often want to "stop the clock" for  change lead time on weekends, holidays, and other "non-working" hours. You can new set working both for your organization and for individual users. Refer to the help to lear more.

New Tutorial: Create your own Custom Automation

Interested in creating a Sleuth Custom Automation for your team or organization, but not quite sure where to start? Or maybe you just need some inspiration?

We got you covered with our most recently published tutorial, "Delete Sync Meetings from Your Calendar with Sleuth Automations".

This tutorial specifically covers how to add a comment on a Jira issue when a deploy contains a Pull Request with a specific label. Along the way we cover how re-use YAML from existing Sleuth Automations and go into details about the building blocks for any Custom Automation.


Auto-update pull requests with Sleuth!

Sleuth Automations can now update pull requests.

Whether it's automatically closing stale PRs, adding PR labels to provide context to PR reviewers, or commenting on PRs to let authors know when their changes have deployed, these 6 new automations help keep things moving while teams focus on what matters: shipping customer value. 

Check out the help doc to learn more, or head over the the Marketplace to give them a try! 

Sleuth can now ignore pull requests!

Whether it's Dependabot or a one-off, unusually long deploy time, sometimes you just need to tell Sleuth to ignore certain PRs - and now you can!

You can manually ignore those one-offs from right within Sleuth, or use Sleuth Automations to set up rules to automatically ignore PRs that meet certain criteria (e.g. those pesky Dependabots). Check out the help doc for more information.


Custom Automations are now on Marketplace!

We've added a new automation to the Marketplace that lets you quickly create and deploy your own custom automations using our YAML-based rules framework!

The quickest way to get started is to copy the YAML from an existing automation or from our automations cookbook, then tweak it to meet your unique needs.

Check out the help doc for more information, or head on over to the Marketplace to start building custom automations now.

Visibility into broken integrations 👀

Sleuth now makes it obvious whenever it detects that an integration has stopped working. 

A warning icon now displays in Sleuth's global navigation bar whenever Sleuth detects a broken integration. The icon links to a central page that provides details about the nature of any broken integrations and how to resolve them. 

We're currently detecting broken code deployment and feature flag integrations, and soon we'll be adding functionality to detect broken impact sources and other integration types. 

We're excited about how this new capability will help ensure the health and trustworthiness of your Sleuth ecosystem and, as always, we welcome your feedback on this and all Sleuth features!

"Deploy-registration-only" API tokens

Sleuth now supports limited API tokens just for registering deploys!

These limited-access tokens are useful when you want to create API tokens that allow integrated tools to register deploys in Sleuth without giving them the ability to do all the other things that Sleuth's standard org-level API token can do. Check out the help doc to learn more. 


Show Previous EntriesShow Previous Entries