burndown chart show inaccurate data
Summary
Burndown chart shows inaccurate data when issues are created before milestone start date and closed after milestone end date.
Steps to reproduce
- Create a few issues
- Create milestone and set start date and end date in the future
- Wait for milestone to expired
- Close the issues
- Observe no changes to the burndown chart
Example Project
https://gitlab.com/groups/gitlab-bronze/-/milestones/1
What is the current bug behavior?
The burndown chart is not showing accurate number of tickets opened at the milestone start date; neither showing accurate number of ticket closed.
What is the expected correct behavior?
- Burndown chart shows exact number of tickets open at the milestone start date.
- Burndown chart shows exact number of tickets closed at the milestone end date as well as ticket closed after milestone end date.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
Gitlab.com, GitLab Enterprise Edition 12.7.0-pre 7ed33754
Affecting customers:
- Bronze SMB with 7 seats https://gitlab.zendesk.com/agent/tickets/142393 (internal)
Edited by Sokunrotanak Srey (Rotanak)