Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Change Requests] - Find work packages affected by a blocking WP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
Context
When a WP’s timeline changes, we need to know which other work packages are blocked by it so those teams can be notified.
Task
Add a backend helper that takes a WP whose timeline has changed and finds the work packages it blocks using the existing WBS_Element.blocking relation.
Return the affected WPs along with the heads/leads and team Slack channels needed for notification.
Acceptance Criteria
- The helper finds all WPs directly blocked by the changed WP.
- Cross-project blocking relationships are included.
- The affected WP’s heads/leads and team Slack channels are returned.
- Duplicate recipients/channels are avoided.
- A WP that blocks nothing returns an empty result.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the backend WBS_Element.blocking relation and any existing helpers for WP heads, leads, and team Slack channels. Verify the helper across project boundaries, deduplicates recipients and channels, and returns an empty result when no WPs are blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100