Allow user to get path to project iteration report within project iteration context

What is currently happening

When the user is on the iterations page within a project (/gitlab-org/gitlab-test/-/iterations) and they click on an iteration, they are taken to the iteration report within a group (/groups/gitlab-org/-/iterations/1).

The path /groups/gitlab-org/-/iterations/1 is taken from project.iterations.webPath in GraphQL:

query {
  project(fullPath: "gitlab-org/gitlab-test") {
    iterations{
      nodes {
        webPath
      }
    }
  }
}

What should happen

When the user clicks on an iteration within a project, they should be taken to an iteration report within a project. For the frontend to do this, it needs to get the path from the backend via GraphQL.

The project iteration report path will probably be something like project/-/iterations/inherited/id rather than project/-/iterations/iid path since we want to view a group iteration which doesn't have a project iid.

Questions:

• Is it possible to have group.iterations.webPath return the group iteration report path and project.iterations.webPath return the project iteration report path? And could this work with top-level query iterations (!38692 (merged))?

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.