GraphQL API - Projects V2 - custom fields nodes don't exist if value not set #118676
Replies: 3 comments
-
Mention: @LumaKernel |
Beta Was this translation helpful? Give feedback.
-
Possibly related: https://github.com/orgs/community/discussions/72181 |
Beta Was this translation helpful? Give feedback.
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Hi! Our team is utilizing GraphQL API to automate and organize our projects and repositories but we have come by a limitation for which there seemingly isn't a workaround.
Question
Body
Custom fields nodes don't exist if value not set - and Initial values can not be set on custom fields.
That is:
Example query:
Response On new issue:
After setting custom field value (example set: int(55)):
(this (getting field ID) is what I expect even if value is not set)
Is there any other way to manage custom fields (for which fieldID is needed) if values are not set?
Beta Was this translation helpful? Give feedback.
All reactions