Add GraphQL mutation to promote an issue to an epic

What does this MR do?

Exposes promote issue to epic through GraphQL mutation

Promote to epic within project parent group

• GraphqQL mutation

mutation {
  promoteToEpic(input: {
    projectPath: "gitlab-org/gitlab-shell", 
    iid: "1"     
  }) {    
    issue {
      id
      iid
      title
      state
      milestone {
        id
        title
      }
    }
    epic {
      id
      iid
      title
    }
    errors
  }
}

• Response with success

{
  "data": {
    "promoteToEpic": {
      "issue": {
        "id": "gid://gitlab/Issue/2",
        "iid": "1",
        "title": "First issue",
        "state": "closed",
        "milestone": {
          "id": "gid://gitlab/Milestone/9",
          "title": "v3.0"
        }
      },
      "epic": {
        "id": "gid://gitlab/Epic/5",
        "iid": "3",
        "title": "First issue"
      },
      "errors": []
    }
  }
}

• Response with error

{
  "data": {
    "promoteToEpic": {
      "issue": {
        "id": "gid://gitlab/Issue/2",
        "iid": "1",
        "title": "First issue",
        "state": "closed",
        "milestone": {
          "id": "gid://gitlab/Milestone/9",
          "title": "v3.0"
        }
      },
      "epic": null,
      "errors": [
        "Issue already promoted to epic."
      ]
    }
  }
}

Promote to epic to a specified group

• Graphql mutation

mutation {
  promoteToEpic(input: {
    projectPath: "gitlab-org/gitlab-shell", 
    iid: "1",
    epicGroupPath: "gitlab-org/gitlab-sugroup-1"
  }) {    
    issue {
      id
      iid
      title
      state
      milestone {
        id
        title
      }
    }
    epic {
      id
      iid
      title
    }
    errors
  }
}

• response with success

{
  "data": {
    "promoteToEpic": {
      "issue": {
        "id": "gid://gitlab/Issue/2",
        "iid": "1",
        "title": "First issue",
        "state": "closed",
        "milestone": {
          "id": "gid://gitlab/Milestone/9",
          "title": "v3.0"
        }
      },
      "epic": {
        "id": "gid://gitlab/Epic/6",
        "iid": "1",
        "title": "First issue"
      },
      "errors": []
    }
  }
}

• response with error

{
  "data": {
    "promoteToEpic": {
      "issue": {
        "id": "gid://gitlab/Issue/2",
        "iid": "1",
        "title": "First issue",
        "state": "closed",
        "milestone": {
          "id": "gid://gitlab/Milestone/9",
          "title": "v3.0"
        }
      },
      "epic": null,
      "errors": [
        "Issue already promoted to epic."
      ]
    }
  }
}

Promote to epic to an inexistent group

• Graphql mutation

mutation {
  promoteToEpic(input: {
    projectPath: "gitlab-org/gitlab-shell", 
    iid: "1",
    epicGroupPath: "gitlab-org/gitlab-sugroup-1/abracadabra"
  }) {    
    issue {
      id
      iid
      title
      state
      milestone {
        id
        title
      }
    }
    epic {
      id
      iid
      title
    }
    errors
  }
}

• response

{
  "data": {
    "promoteToEpic": null
  },
  "errors": [
    {
      "message": "The resource that you are attempting to access does not exist or you don't have permission to perform this action",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "promoteToEpic"
      ]
    }
  ]
}

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

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

Related to #233974 (closed)

changed milestone to %13.6

added Category:Issue Tracking Deliverable auto updated backend cm-scorecard-rec devopsplan direction featureenhancement frontend groupproject management issues sectiondev workflowin dev labels

added typefeature label

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/graphql/reference/index.md

The review does not need to block merging this merge request. See the:

• Technical Writers assignments for the appropriate technical writer for this review.
• Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited, or the chosen person is unavailable.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Category	Reviewer	Maintainer
backend	Reuben Pereira (@rpereira2) (UTC+5.5, 3.5 hours ahead of @acroitor)	Luke Duncalfe (@.luke) (UTC+13, 11 hours ahead of @acroitor)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

• 87849dc8 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added documentation label

added 946 commits

• 87849dc8...6f1d8cbd - 946 commits from branch 233974-promote-issue-to-epic-refactoring

Compare with previous version

changed target branch from 233974-promote-issue-to-epic-refactoring to master

changed the description

added 1 commit

• 90eb243e - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added 233 commits

• 90eb243e...9d760370 - 232 commits from branch master
• 8b01dfc2 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added 1 commit

• 1be41f77 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added 198 commits

• 1be41f77...c0c28d30 - 197 commits from branch master
• 17c0bd61 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

changed the description

changed the description

added 1 commit

• 21eb9402 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

marked the checklist item Changelog entry as completed

marked the checklist item Documentation (if required) as completed

@furkanayhan mind taking a look please ?

assigned to @furkanayhan

approved this merge request

unassigned @furkanayhan

added 345 commits

• 21eb9402...8cdba719 - 344 commits from branch master
• 8139e2d6 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

resolved all threads

added 1 commit

• bee1664f - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

@lulalala would you please take the maintainer review ?

assigned to @lulalala

I also don't have much experience in GraphQL either. Could I ask for an extra pair of eye on this?

Hi @egrieff would you have time to review this please? I see you have worked on SetEpic in the past. Thanks

assigned to @egrieff

unassigned @egrieff

added 466 commits

• bee1664f...e6b32c6f - 465 commits from branch master
• 2bea1609 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added 1 commit

• 1523c5c4 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

added 356 commits

• 1523c5c4...e44498c4 - 355 commits from branch master
• 7a36f6d3 - Add GraphQL mutation to promote an issue to an epic

Compare with previous version

approved this merge request

resolved all threads

enabled an automatic merge when the pipeline for 697e0d86 succeeds

merged

mentioned in commit 4500f057

mentioned in commit c323b25d

mentioned in commit a5039868

added workflowstaging label and removed workflowin dev label

added workflowcanary label and removed workflowstaging label

added workflowproduction label and removed workflowcanary label

mentioned in issue gitlab-com/www-gitlab-com#8990 (closed)

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added Category:Team Planning label