Skip to content

Use top-level iterations query for project iterations report

What does this MR do?

Iterations at a group level has now been released. Issue #222763 (closed) aims to show iterations at project level.

This MR:

  • Uses the iteration GraphQL field for the project iteration report
  • Updates GraphQL queries so both groups and projects can use them
  • Uses the new project/iterations/inherited/show route
  • Deletes the old project/iterations/show route
  • Renames groupPath to fullPath

These changes are part of a feature which is behind the feature flag project_iterations, defaulted to off.

This MR is part of a sequence of changes:

  1. An MR to add a bare Iterations page in projects (!37715 (merged))
  2. An MR to show a list of iterations on the Iterations page in projects (!37961 (merged))
  3. An MR to show an iteration report within a project (!37979 (merged))
  4. An MR to update to use the project iterations GraphQL query for the project iterations list (!38705 (merged))
  5. An MR to update to use the top-level iterations GraphQL query for the project iterations report (this MR)

Screenshots

Screenshot_2020-08-06_at_7.00.40_pm

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Coung Ngo

Merge request reports