[Bug] Project Auto-Intake Workflow Not Mapping Fields Correctly

[erifystudio]

Describe the bug

When creating or labeling issues/PRs, the auto-intake workflow sometimes fails to map Priority, Size, or Cycle fields in ERIFY Studio Team Planning (4PW).

To Reproduce

Steps to reproduce the behavior:

1. Create a new issue with priority:P1 and effort:M labels.
2. Observe the issue being auto-added to the Project.
3. Check the Project fields → Priority and Size remain unset.

Expected behavior

• Priority field should map to P1 (High).
• Size field should map to M (Medium).
• If labeled planned, the issue should move into Cycle @current.

Screenshots / Logs

If applicable, add screenshots or logs here.
Ex: GitHub Actions run shows success but fields are blank.

Environment

• Repo: erifystudio/erify-world
• Project: ERIFY Studio Team Planning (4PW)
• Workflow: .github/workflows/project-auto-intake.yml

Additional context

This bug blocks accurate capacity planning and roadmap views, since fields are essential for metrics and iteration tracking.

[erifystudio]

Thanks for flagging this. 🙏

I’ll investigate why Priority / Size / Cycle fields aren’t mapping correctly.
Initial suspicion:

• Field name mismatch between Project and Action config.
• Label parsing may not be trimming prefixes (e.g., priority:P1 vs P1).
• Iteration mapping might not detect the active @current cycle.

Next steps:

• Check the workflow logs for field update failures.
• Verify the Project field names (Priority, Size, Cycle) match exactly.
• Add debug output for label-to-field matching.
• Patch the Action to normalize label strings.

Will update here with progress. 🔥

[erifystudio]

Acknowledged ✅

Thanks for raising this bug. We’ll use this thread to track progress.

🔍 Initial focus areas:

• Verify workflow logs for field update failures.
• Confirm Project field names (must match exactly: Priority, Size, Cycle, Completed At).
• Test label mappings (priority:P1, effort:M, planned) on a fresh issue.
• Add debug logging in the Action to trace values being sent to GraphQL.

📌 Goal: ensure all fields map correctly so that capacity and roadmap views stay accurate.

I’ll report back here once we replicate and isolate the root cause. 🚀

[erifystudio]

Thanks for reporting this bug 🙏

We’re tracking it under ERIFY Studio Team Planning (4PW).

Next steps:

• Reproduce the issue with a test label set (priority:P1, effort:M, planned).
• Inspect the workflow logs for any GraphQL field update errors.
• Confirm field names in the Project (Priority, Size, Cycle, Completed At).
• Add debug logging to see exactly which values are passed.

I’ll update here as soon as we isolate the cause. 🚀

[erifystudio]

Noted 👌 I’ll continue monitoring this issue.
Once the workflow fix is tested, I’ll post the results here so the Project fields (Priority, Size, Cycle) update correctly. 🔍⚡