OR for Events in Cycle Analytics

Problem to solve

In Cycle Analytics one of the stages has a multi-part definition; the Issue stage is defined as "the time from Issue creation to the first comment or MR creation". Often users might also want to define a stage based on 2 events, for example: 1) an issue is added to a milestone OR a board 2) an MR for an issue is closed OR the label 'in QA' is added (AND, ex: 3) an issue has been mentioned in a commit and an MR is created, will be considered in the next milestones)

Follow up on: https://gitlab.com/gitlab-org/gitlab-ee/issues/12196

Intended users

EMs, Directors, PMs

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

Solution

Step 1 Step 2 Step 3
image image image
  • We always show the 'Add another start event' link at the bottom of the Start event(s) table
  • We only show the 'Add another stop event' link once at least one start event has been added (at the same time we hide the 'Please select a start event first' message below the stop event dropdown
  • I recommend we use segmented control for the object types as it'll slightly improve the usability
  • the user should be able to add as many up to 2 start/stop events without filling in the actual data. They can do that after they added the number of events they need
  • the user can delete all start/stop events but the first one. A browser-native alert for confirming the delete action should be enough for now.
  • EDIT 2019-09-13 by @djensen: Changed spec to limit conditions to 2 events per #12883 (comment 216847092)
  • EDIT 2019-09-17 by @djensen: Described the default definition of the Issue stage in the "Problem to Solve".

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖