Skip to content

Iteration Report: Project-level view shows Group-level burndown

Summary

An Iteration created at the Group level and viewed at the Project level shows a burndown and burnup chart for the entire Group, while the counts and issue list are scoped only to the Project.

Steps to reproduce

  1. Create a Group with at least 2 Projects
  2. Create a new Iteration for the Group
  3. Add at least one Issue to the Iteration from each of at least 2 Projects
  4. Navigate to one of the Projects, then open the Iteration Report for the Iteration created above
  5. View the Burndown Chart and Burnup Chart issues relative to the Issue Counts at the top and Issue List at the bottom, note the inconsistency

Example Project

https://gitlab.com/iteration-burndown-test/project1/-/iterations/17637

What is the current bug behavior?

The behavior we observe is that the Project-level view correctly lists the issues (and issue count) just associated with that Project, however the Burndown and Burnup charts seem to include issue counts / issue weights for the entire Group (and thus don't match the rest of the report).

What is the expected correct behavior?

We expected that the Group-level Iteration Report would show the full burndown of all issues tagged in the Iteration, while the Project-level Iteration Report would show the burndown for just the issues in that Project tagged in the Iteration.

Relevant logs and/or screenshots

image

Output of checks

This bug happens on gitlab.com (we first encountered it on our company's self-hosted Gitlab running 13.9.4)

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes