Projects where most issues created has milestones will display "Not enough data" for Cycle Analytics
Summary
A project my company has on Gitlab.com says "Not enough data" for the Issue
stage. It is likely due to the fact that our median is 0. Considering that our project is private, and issues we create are almost always assigned a milestone during creation, it means we are stuck with "Not enough data" instead of "0".
We mostly use ~4 milestones at a time, e.g. current sprint, next sprint, future or something similar. It feels weird that it says "Not enough data", considering that we feel like there is loads of data available.
The first screenshot below (partly anonymized via filter: blur(5px)
) shows our the view from our private project. I found #45298 (moved), which likely explains why our "Plan" stage is empty, why both "Plan" and "Code" has "Not enough data". That "Issue" is missing data with 50+ events led me to create this issue.
Steps to reproduce
- Create a new project
- Create a milestone
- Create some issues where the milestone is pre assigned on all or most of them (I think I created way more issues than I needed)
- Do the rest of the steps to get issue deployed to production for circle analytics
- Create a
.gitlab-ci.yml
with aproduction
environment job (I usedwhen: delay
) onmaster
- Create commit referring to issue in message (with #XXX) on a branch
- Create merge request for branch with
Closes #XXX
message - Merge the MR
- Repeat 2) => 4) for new issues a couple of times (1-2?) until cycle analytics is mostly populated
- Create a
- Check the Cycle Analytics tab
Hopefully (or not) it looks like the second screenshot in the section below.
Example Project
https://gitlab.com/csvn/cycle-analytics-issue-bug/cycle_analytics
(data will only be available for 90 days, after that ping me if I need generate some more events
What is the current bug behavior?
"Issue" says "Not enough data".
What is the expected correct behavior?
"Issue" shows "0 seconds" or a friendlier message like "Empty median" (maybe with a link?)
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Possible fixes
Sorry, I have no idea. Frontend engineer with no Ruby experience