fix: refactor proposal cloning logic to ensure correct user permissio… - #1287
Merged
jekabs-karklins merged 13 commits intoJan 13, 2026
Merged
Conversation
jekabs-karklins
requested review from
deepaksftc and
mutambaraf
and removed request for
a team
December 8, 2025 19:13
…oposal membership
…hub.com:UserOfficeProject/user-office-core into SWAP-5131-uo-could-not-clone-the-proposal-error
mutambaraf
approved these changes
Jan 13, 2026
jekabs-karklins
deleted the
SWAP-5131-uo-could-not-clone-the-proposal-error
branch
January 13, 2026 11:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the bug where it was not possible to clone proposal if user was already on the proposal. The issue was that the check if user was write permissions on the clonned proposal was done before users were added. This resulted in
duplicate key value violates unique constraintexception.After discussing the issue with UO, i have adjusted the logic to add user to be a co-proposer on the cloned proposal only if he has a user role and is not already part of it. This keeps it more straight forward.
@mutambaraf let me know if this logic is also ok with you.
Motivation and Context
Rework logic on when user is added a co-proposer for the cloned proposal.
Changes
TemplateDataSourcefromProposalMutations.ts, as it was not used.How Has This Been Tested?
Fixes Jira Issue
https://jira.esss.lu.se/browse/SWAP-5131
Depends On
Tests included/Docs Updated?