Accessing new Issue Type and ProjectV2 Fields in REST API #147117
Replies: 2 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
I’m trying to work with the new
issue type
field and theProjectV2
fields, but I’m running into some obstacles.As far as I can tell, these fields aren’t currently exposed through the REST API, and while I know they’re available via GraphQL, it seems like I can’t retrieve them for a specific issue without iterating through all issues in a project.
That feels a bit cumbersome, especially if we’re dealing with a large number of records.
I might be missing something—maybe there’s a way to do this that I’m not aware of. If that’s the case, I’d love some guidance. But if not, is this something on the roadmap for the REST API or the generated Kiota-based API client? Being able to filter and query based on a single issue would be incredibly helpful, and having these fields exposed on the REST side would streamline the process a lot.
Any insights or recommendations would be greatly appreciated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions