<!-- The first four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> As we created a webhook for deployment events, we wanted to include started which will help users calculate cycle times with deployment activities. ### Proposal Add started to webhook events ### Note It's highly coupled with https://gitlab.com/gitlab-org/gitlab/-/issues/235475, so it will take less effort to work on these 2 issues simultaneously.