Move Work wizard says "You do not have any projects" despite open user-owned Projects

[A1-NWS-Dev1]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Body

What are you trying to do?

I am trying to use GitHub's native Move work to an organization workflow to move repositories and GitHub Projects from my personal account to an organization that I own.

I am an Owner of the destination organization. Projects are enabled for the organization, and I can create organization Projects.

GitHub's documentation states:

"You can transfer repositories and projects from your personal account to a new or existing organization through your account settings."

Documentation:
https://docs.github.com/en/account-and-profile/how-tos/account-management/moving-your-work-to-an-organization

What did you expect to happen?

I expected the Move work to an organization wizard to list my open, user-owned GitHub Projects so that I could select them for transfer to the organization.

The personal account currently owns two open Projects.

What happened instead?

The Move Work wizard correctly detects and lists repositories owned by my personal account.

However, the Projects section displays:

You do not have any projects

This occurs even though the personal account owns two open GitHub Projects.

Verification

GitHub CLI correctly detects both Projects:

gh project list --owner <PERSONAL_ACCOUNT>

NUMBER  TITLE                STATE
2       <PRIVATE PROJECT>    open
1       <PRIVATE PROJECT>    open

I also verified one of the Projects directly using:

gh project view <PROJECT_NUMBER> --owner <PERSONAL_ACCOUNT> --format json

The relevant portion of the response is:

"closed": false,
"owner": {
  "login": "<PERSONAL_ACCOUNT>",
  "type": "User"
}

Therefore, GitHub's API/CLI recognizes the Project as an open Project owned by the user account.

Destination organization

I have confirmed that:

• I am an Owner of the destination organization.
• GitHub Projects are enabled for the organization.
• I can create new Projects in the organization.
• The Move Work wizard successfully detects my personal repositories.

Steps to reproduce

1. Have an open GitHub Project owned by a personal account.
2. Go to Settings → Organizations.
3. Select Move work to an organization.
4. On the page for selecting work to move, observe that personal repositories are listed.
5. Check the Projects section.

Actual result:

You do not have any projects

Expected result:

The open user-owned Projects should be available for selection, consistent with GitHub's documentation for moving repositories and projects from a personal account to an organization.

Troubleshooting already performed

I have verified that:

• The Projects are open.

• The Projects are owned by the personal account.

• gh project list successfully enumerates them.

• gh project view reports the owner type as User.

• I am an Owner of the destination organization.

• Projects are enabled in the destination organization.

• I can create organization Projects.

• The Move Work wizard successfully detects personal repositories but reports zero Projects.

• I also contacted GitHub Support and received a response from a GitHub Support representative. I was advised that the support resources available for my account are GitHub Community Discussions, Docs, and Skills, and the ticket was closed without investigating why the Move Work wizard fails to detect the open, user-owned Projects that GitHub CLI successfully recognizes.

Related discussion

I found this related Community discussion about moving a personal Project to an organization:

https://github.com/orgs/community/discussions/193246

The Move Work workflow is suggested there, but I have not found a discussion explaining why open user-owned Projects would fail to appear in the Move Work wizard.

Question

Are there additional eligibility requirements for user-owned GitHub Projects to appear in the Move work to an organization wizard?

If not, could this be a bug in the wizard's Project enumeration or eligibility logic?

I would prefer to use GitHub's documented native transfer mechanism rather than copy or reconstruct the existing Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[DecoyVr]

This appears to be a limitation or bug in the Move work to an organization workflow rather than an issue with the Projects themselves.

The important point is that the Projects are demonstrably valid and user-owned:

• gh project list --owner <PERSONAL_ACCOUNT> successfully returns both Projects as open.
• gh project view <PROJECT_NUMBER> --owner <PERSONAL_ACCOUNT> --format json reports "closed": false.
• The Project owner is confirmed as type: "User".
• You are an Owner of the destination organization.
• Projects are enabled for the destination organization and you can create organization Projects.
• The Move Work wizard can detect your personal repositories, but incorrectly reports “You do not have any projects.”

Based on those checks, there does not appear to be an obvious eligibility requirement that would explain why the Projects are missing.

One possibility is that the Move Work wizard is using different eligibility/enumeration logic from the GitHub Projects API/CLI. In other words, the Projects can be queried successfully through the API but are not being returned by the UI’s transfer workflow.

I would therefore treat this as a likely GitHub UI/workflow bug or an undocumented limitation, rather than an incorrectly configured Project.

The most useful next step would be for GitHub to confirm exactly which API/query the Move Work wizard uses to enumerate transferable Projects and what eligibility conditions it applies. If the two open user-owned Projects satisfy those conditions, the wizard should presumably list them for transfer.

Until GitHub confirms otherwise, I would not recreate or manually copy the Projects, since the documented Move work to an organization workflow is specifically intended to handle moving personal work into an organization.

[A1-NWS-Dev1]

Thank you. Will wait on Github action / response.