Skip to content

Allow to reference board in ancestor group when creating epic

Jan Provaznik requested to merge jp-board_epic into master

What does this MR do?

When an epic is created from an epic board, user can can select a group where the epic will be created. This group can be either the same group as board's group or any subgroup.

For this reason when we are searching for the board, it can exist in any ancestor group.

Related to #336645 (closed)

DB queries:

Screenshots or Screencasts (strongly suggested)

How to setup and validate locally (strongly suggested)

Sample graphql query:

mutation {
  boardEpicCreate(input: {boardId: "gid://gitlab/Boards::EpicBoard/1", groupPath: "h5bp/sgroup1", listId: "gid://gitlab/Boards::EpicList/1", title: "test3"}) {
    epic {
      id
      title
    }
    errors
  }
}

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • 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 Jan Provaznik

Merge request reports

Loading