Skip to content

Bugfix/needs stories sprint label scope#80

Merged
Juce-me merged 2 commits into
mainfrom
bugfix/needs-stories-sprint-label-scope
Jun 16, 2026
Merged

Bugfix/needs stories sprint label scope#80
Juce-me merged 2 commits into
mainfrom
bugfix/needs-stories-sprint-label-scope

Conversation

@Juce-me

@Juce-me Juce-me commented Jun 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fix Needs Stories / Backlog alert scope so selected future sprint labels are considered when deciding whether an epic belongs to the selected planning sprint.
  • Route Needs Stories alert grouping through configured team labels instead of relying only on the Jira Team field.
  • Pass configured team labels from the ENG frontend task loader to the backend task endpoint.
  • Include team label scope in the task cache key so different planning-team scopes cannot reuse stale alert payloads.

Validation

  • npm run build
  • .venv/bin/python -m unittest discover -s tests
  • node --test tests/test_*.js
  • Live Basic-auth route check confirmed the referenced label-scoped epics are included in the alert payload.

Juce-me added 2 commits June 16, 2026 17:44
Group future-planning epic alerts from configured team-label mappings so multi-label epics appear under every matching planning team. Carry selected sprint labels into the epic scope so label-scoped planning epics are not misclassified as backlog.
Carry configured team labels through the task request so empty-epic alerts can discover label-scoped epics even when their Jira Team field differs. Include label scope in the task cache key because it changes the epics returned for alert grouping.
@Juce-me Juce-me merged commit 5c19db0 into main Jun 16, 2026
@Juce-me Juce-me deleted the bugfix/needs-stories-sprint-label-scope branch June 16, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant