Skip to content

#4246 proposed changes + task extras - #4353

Merged
wavehassman merged 4 commits into
developfrom
#4246-proposed-changes+task-extras
Jul 31, 2026
Merged

#4246 proposed changes + task extras#4353
wavehassman merged 4 commits into
developfrom
#4246-proposed-changes+task-extras

Conversation

@wavehassman

@wavehassman wavehassman commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Wbs_Proposed_Changes
  • Project_Proposed_Changes
  • Work_Package_Proposed_Changes
  • Added task labels and blocking

Checklist

It can be helpful to check the Checks and Files changed tabs.
Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.

  • All commits are tagged with the ticket number
  • No linting errors / newline at end of file warnings
  • All code follows repository-configured prettier formatting
  • No merge conflicts
  • All checks passing
  • Screenshots of UI changes (see Screenshots section)
  • Remove any non-applicable sections of this template
  • Assign the PR to yourself
  • No yarn.lock changes (unless dependencies have changed)
  • Request reviewers & ping on Slack
  • PR is linked to the ticket (fill in the closes line below)

Closes #4246

@wavehassman wavehassman self-assigned this Jul 25, 2026
@wavehassman
wavehassman marked this pull request as ready for review July 25, 2026 23:52
@wavehassman wavehassman changed the title #4246 proposed changes+task extras #4246 proposed changes + task extras Jul 25, 2026

@Santiordon Santiordon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking great so far!

? parent.managerId
: pickDifferentActor(
faker,
ownerCandidates,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks strange to me. Is this intentional? We are using ownerCandidates for both lead and manager even though they are different roles. Also, we are not guarding a case where both the lead and manager for the PC is the same.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ownerCandidates-for-both-fields part is intentional because the real service functions (createActivationChangeRequest/createLeadershipChangeRequest) don't distinguish lead vs. manager eligibility by role.

Making the guard rn!

Comment thread src/backend/src/prisma/factories/tasks.factory.ts Outdated
Santiordon
Santiordon previously approved these changes Jul 27, 2026

@Santiordon Santiordon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

Steph375
Steph375 previously approved these changes Jul 28, 2026
@wavehassman
wavehassman dismissed stale reviews from Steph375 and Santiordon via 4ba851a July 31, 2026 00:01
@wavehassman
wavehassman merged commit f43ab0b into develop Jul 31, 2026
4 checks passed
@wavehassman
wavehassman deleted the #4246-proposed-changes+task-extras branch July 31, 2026 00:08
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.

[Seed Data] -Generate Proposed WBS Change Data

3 participants