Updated bulk move issues milestone in the docs

What does this MR do and why?

Follow-up from !95688 (merged).

In this MR I update/fix the milestone mentioned in the docs related to the bulk move issues feature 🙂

Related to Bulk move issues to a different project (#15991)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

added Leading Organization label

Hey @zillemarco! 👋

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help moving the MR forward, feel free to post @gitlab-bot help. Read more on how to get help.

To enable automated checks on your MR, please configure Danger for your fork.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @zillemarco

Hi @msedlakjakubowski 👋 🙂 Here is the fix for the milestion on the documentation 🙂 Could you please review? 🙏 Thanks a lot 🙂

@gitlab-bot ready @msedlakjakubowski

added workflowready for review label and removed workflowin dev label

requested review from @msedlakjakubowski

Hi @sarahgerman! Please review this documentation merge request. This message was generated automatically. You're welcome to improve it.

added documentation twtriaged labels

requested review from @sarahgerman

@msedlakjakubowski @sarahgerman, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
• Add the workflowin dev label if the merge request needs action from the author. This message was generated automatically. You're welcome to improve it.

added 1 commit

• 4cef3032 - Updated bulk move issues milestone in the docs

Compare with previous version

removed review request for @sarahgerman

changed milestone to %15.6

added Technical Writing docsfix maintenancerefactor twdoing typemaintenance workflowin review labels and removed twtriaged workflowready for review labels

changed the description

approved this merge request

resolved all threads

	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/user/project/issues/managing_issues.md

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

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

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

Generated by 🚫 Danger

	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/user/project/issues/managing_issues.md

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

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

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

Generated by 🚫 Danger

merged

@zillemarco, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a 👍 or a 👎 on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help! ❤

This message was generated automatically. You're welcome to improve it.

mentioned in commit 6981e481

mentioned in merge request !95688 (merged)

added workflowstaging-canary label and removed workflowin review label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedcandidate label

mentioned in merge request kubitus-project/kubitus-installer!1646 (merged)

added releasedpublished label and removed releasedcandidate label