Why does createIssue fail with a valid projectIds value?

[JeelGajera]

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.

[benjie]

Hi @JeelGajera, from the endpoints you mention I'm guessing this is an issue with the GitHub GraphQL API? You should probably direct your query to GitHub; one such forum would be:

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

This repository is the reference implementation of GraphQL but doesn't relate to GitHub specifically (in fact, I think GitHub use Ruby, not JS?)