Skip to content

Allow private engagements without active assignments - #23

Merged
jmgasper merged 2 commits into
masterfrom
develop
Jul 7, 2026
Merged

Allow private engagements without active assignments#23
jmgasper merged 2 commits into
masterfrom
develop

Conversation

@jmgasper

@jmgasper jmgasper commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

jmgasper added 2 commits July 2, 2026 09:33
What was broken
Private engagements were forced to have at least one active assigned member. After the last assignment was completed or removed, saving the engagement to mark it completed failed because there were no active assignments left.

Root cause
The engagement service treated privacy as requiring an active assignment during create, update, and assignment-removal flows, even though completed assignments are terminal history and private engagements can still require members without currently assigning one.

What was changed
Removed the active-assignment requirement for private engagements while keeping the guard that prevents assigning more active members than requiredMemberCount. Updated the assignment-removal documentation to match the new behavior. Kept lint-required formatting fixes produced by the repo lint command.

Any added/updated tests
Added service tests covering private engagement creation without an assigned member, marking a private engagement closed after all assignments are completed, and removing the final active assignment from a private engagement.
PM-5504: Allow private engagements without active assignments
@jmgasper
jmgasper merged commit 6587ce0 into master Jul 7, 2026
6 checks passed
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