Skip to content

Unable to move issue to another project - target project not in the list

Problem to solve

Sometimes it is not possible to move an issue from one project to another, because the target project cannot be found in the list.

Further details

The ability to move an issue from one project to another was introduced in 8.6 (see the implementation issue and the blog post). Now, on the Issue page, there is a button at the bottom of the right-side controls to "Move issue". If you click that button, a dropdown appears for you to select the target project. If you don't see what you are looking for in the list of 20 projects, you can enter text in the "Search project" input. Search results are also limited to 20 projects. So if you aren't able to find what you are looking for in the default list, or with search, then you cannot move the issue.

Example

  1. Go to https://gitlab.com/gitlab-org/manage/-/issues/16361 (internal link)
  2. Click the button to "Move issue"
  3. Attempt to find the gitlab project - it apparently cannot be found

Proposal

Backend should sort the "Search project" response by best matches, so the top 20 best matches are displayed (instead of an arbitrary 20 results from all the matches).

Performance

Backend should continue to limit the number of projects returned, for performance reasons.

Permissions and Security

No permissions or security implications.

What does success look like, and how can we measure that?

The example issue above can be successfully moved to the gitlab project.

Links / references

cannot_move_issue

Edited by Dan Jensen