Trace code changes to issue tickets

Free technical webinar by Datree & CircleCI

Thank you! We'll send you an email shortly with the link to the guide.
Oops! Something went wrong. Please try again or contact info@datree.io for assistance.

Referencing an issue tracker ticket number in every code change is considered a development best practice for better collaboration and trackability. For teams that need to achieve or maintain compliance with standards like SOC 2, it is also a mandatory policy.

With the new Datree Orb for CircleCI, you can quickly implement an automatic policy check on every build to ensure pull request titles and branch names always include a ticket number.

In this webinar, we'll cover the benefits of adopting this best practice, and how to implement it in a scalable way as your team and codebase grow.


Hosted by:

Shimon Tolts

Shimon is the Co-founder and CEO of Datree.io, an AWS Community Hero, and a frequent speaker on the topic of DevOps.

Sam Olukotun

Previously a full stack engineer, Sam now helps CircleCI customers adopt best practices in CI/CD as a Solutions Engineer.

Register for the webinar

Thank you! We'll send you an email shortly with the link to the guide.
Oops! Something went wrong. Please try again or contact info@datree.io for assistance.