Launched: Require Comments for Flag Changes and Confirmations for Environment Changes
As teams get larger, it becomes harder for everyone to understand all of the changes made to a system. LaunchDarkly helps you communicate the why of every change with optional comments when making flag changes.
Since the initial release of comments, we have gotten great feedback on how having a little more information about flag changes helps teams stay in sync. This feature has been so helpful that some teams have asked to require comments on every flag change.
Today, we are introducing two new controls for LaunchDarkly teams built on comments. The first is the ability for administrators to make comments required when users change a flag or a segment within certain environments. You can set up required comments when you create a new environment, or you can add them as a requirement to existing environments. For new projects, we’ve turned on the require comments option for the pre-generated production environments. (You can, of course, turn this off.)
The second new control is a new safety net for flag changes to critical environments—you now can set an option to have users type an extra confirmation when making changes to flags in that environment. This new control helps reduce the possibility of accidentally changing a flag in your production or another critical environment.
These new capabilities give your team extra control and confidence using flags. As you scale LaunchDarkly across more projects and even more teams, these confirmations help reduce the likelihood of incorrect changes and help your teams ship faster.
Check out our documentation for more details on requiring comments and environment confirmations. For further questions, please email email@example.com.