[Project Edits] - Ability to change project lead/manager that also changes non-complete work packages
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- full-stack
Research direction
Start at the project edits page and trace the hook that handles lead/manager changes. Then inspect the backend project-edit entry point and service logic for updating associated non-complete work packages. Done means the edit UI exposes the option, the hook and backend accept it, and eligible work packages receive the new lead or manager.
Written by the indexing model from the issue text.
Description
Description
This ticket will involve both frontend and backend work.
Add a checkbox (or other functionality) that a user can check when editing the lead/manager of a project that would cause the change to be made for the non-complete work packages in the project (i.e. the project lead/manager is updated for any corresponding non-complete work packages inside the project).
Acceptance Criteria
- There is something in the project edits page that allows a user to enable the described functionality (can be a checkbox, button, etc.).
- The hook will need to be updated to handle this new input.
- The backend will need to be able to support this new input, and handle the new logic accordingly (associated work packages are updated with the new lead/manager).
Proposed Solution
Update the frontend to support this new input (e.g. checkbox). Change the hook to support this new input. Update the backend to handle this new input, and create the service logic that achieves the described functionality.
Mocks
No response
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
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.
More from Northeastern-Electric-Racing/FinishLine
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in Northeastern-Electric-Racing/FinishLine
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·