soloscrum-tracker-github-set-sp
Records a Subtask's SP value in a GitHub Projects v2 custom field named SP (Number type). Active when tracker_profile = github-only.
Inputs
issue_number— Sub-issue numbersp— story points integer (persoloscrum-define-story-points)project_number— GH Project v2 number, the human-readable id used bygh projectCLI commandsproject_id— GH Project v2 node ID (GraphQL), used by theupdateProjectV2ItemFieldValuemutationfield_id— Project field ID forSP(resolved from project)
Steps
- Add the issue to the project if not already added:
gh project item-add <project_number> --owner <owner> --url <issue_url> - Set the SP field via GraphQL:
gh api graphql -f query=' mutation($project: ID!, $item: ID!, $field: ID!, $value: Float!) { updateProjectV2ItemFieldValue( input: { projectId: $project, itemId: $item, fieldId: $field, value: { number: $value } } ) { projectV2Item { id } } }' -F project=<project_id> -F item=<item_id> -F field=<field_id> -F value=<sp>
Output
- Confirmation of SP set on the project item
Notes
- The Project must have a
SPfield of type Number — if absent, prompt the user to add it once - Issue-level SP (size-check from
/soloscrum:refine) is not stored anywhere; only Subtask SP is registered (persoloscrum-define-story-points) - Project ID and field ID can be cached in
.claude/rules/tracker.mdafter first resolution to skip the lookup