Add additional events to cycle analytics
Problem to solve
Users have different processes that show themselves differently in the data. An example is:
One issue with 2 merge requests - we would like to consider the issue moving to QA once both MRs have been closed, i.e. development phase is done once the last MR associated with the issue (mentions it in the description or subject) is closed.
Example for code review stage:
- Possible start events: New assignee added OR new code is pushed
- Possible end events: approved OR merged OR previously added assignee removed OR new code is pushed
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/models/event.rb
Intended users
Further details
Proposal
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Virjinia Alexieva