GitHub user lucasrabaca edited a discussion: Github Projects v2 as source for story points
**What I'm trying to do:** Populate issues.story_point for issues that come from GitHub, so story-point / velocity metrics work the same way they do for Jira. Some teams set story points on Jira and others on GitHub Projects (v2) board, in a custom number field (e.g. "Estimate"/"Points"). **What I'm seeing:** On our instance, issues.story_point is populated for Jira but always NULL for GitHub: Looking at the raw layer _raw_github_graphql_issues (563 rows), the collected GraphQL payload contains no projectItems / fieldValues (I grepped: projectItems = 0, estimate = 0). So the Projects v2 field values don't seem to be collected at all. **My questions:** Is there a currently supported way to get GitHub Projects v2 custom field values (specifically a numeric story-point field) into issues.story_point — via scope config, a transformation rule, an env flag, or blueprint advanced mode — that I've overlooked? Does the GitHub collector require a specific token scope (e.g. read:project) for Projects v2 data, and could a missing scope be why projectItems is absent from the raw payload? Is there any existing issue/PR or roadmap item for collecting GitHub Projects v2 field values? I couldn't find one, but want to avoid duplicating effort. This is not about the recent implementation of global issue fields, but Projects v2 fields. GitHub link: https://github.com/apache/devlake/discussions/9123 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
