Why does createIssue GraphQL API mutation Fail with a valid projectIds value?

[JeelGajera]

Select Topic Area

Question

Body

I'm encountering an unexpected behavior when using the createIssue mutation with the projectIds field. When I pass a valid project global ID (retrieved from projectsV2 query) in the projectIds array, the mutation fails with a NOT_FOUND error stating, "Could not resolve to Project node with the global id of 'PVT_xxxxxxxxx-xxxx'." However, if I pass an empty array instead or remove this field, the issue is created successfully, and I can later bind the issue to the project using the addProjectV2ItemById mutation.

I have also noticed this if we create issue via github web portal and we assign project it makes two separate calls one is for create issue with parentIds: null and other with addProjectV2ItemById to bind issue into project.

My goal is to have the issue automatically linked to the project at creation time—without needing an additional API call. Is this behavior intended? Are there any known limitations or additional requirements for using projectIds in the createIssue mutation? Any guidance on achieving a one-step project binding would be greatly appreciated.

[Sazidul0]

1. projectIds in createIssue is for Classic Projects
   The projectIds field in the createIssue mutation is only compatible with classic GitHub Projects (not ProjectsV2).
   ProjectsV2 uses a different system and requires the addProjectV2ItemById mutation to associate issues. This explains the NOT_FOUND error when using a ProjectsV2 ID in projectIds.

2. ProjectsV2 Requires a Separate Step
   GitHub’s UI/API intentionally separates issue creation and ProjectsV2 binding. This is why you observe two calls in the web portal:
   Create the issue (no ProjectsV2 association).
   Use addProjectV2ItemById to link the issue to ProjectsV2.
   There is no way to link to ProjectsV2 in a single step during issue creation.

3. Workaround for Automation
   To minimize round trips, use a single request with multiple mutations:

mutation CreateIssueAndLinkToProjectV2($issueInput: CreateIssueInput!, $projectInput: AddProjectV2ItemByIdInput!) {
  createIssue(input: $issueInput) {
    issue {
      id
    }
  }
  addProjectV2ItemById(input: $projectInput) {
    item {
      id
    }
  }
}

[JeelGajera]

Hello @Sazidul0 thanks for clarification of projectIds role in createIssue mutation for classic project and projectV2 but we can't directly reference the output of one mutation as an input for another within the same operation.

I have to create issue first than have to use node_id as a contentId for projectV2 association with addProjectV2ItemById mutation in second request. So I think currently createIssue mutation is not directly compatible with projectV2 so we have to make two api calls.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬