Use a correct group path when fetching an epic in graphql boards
Summary
We should use a correct fullpath
when fetching an epic to display it in the graphql boards sidebar.
Currently, we are using the topmost parent group path as fullpath
when fetching an epic for an issue even when the epic belongs to a subgroup.
Steps to reproduce
- Create an epic and an issue under a subgroup/project then assign the created epic to the issue.
- Use the FF
:grapqhl_board_lists
and visit an issue board for the subgroup. - Click on the issue card.
Example Project
Reproduced following the above instruction in https://gitlab.com/gitlab-org/plan-stage/test-project/-/boards.
-
The subgroup is
plan-stage
: https://gitlab.com/gitlab-org/plan-stage -
The epic titled
epic for plan-stage
belongs toplan-stage
which is a subgroup ofgitlab-org
-
The issue titled
some-issue
is assigned to the epic.
Because we use gitlab-org
as fullpath
rather than gitlab-org/plan-stage
, we get an error when fetching the epic for the issue in the issue boards https://gitlab.com/gitlab-org/plan-stage/test-project/-/boards: