Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ELEMENTS-1652-BACKPORT: prevent replacing and removing an attachment under retention #788

Conversation

Nishant0928
Copy link
Contributor

@Nishant0928 Nishant0928 commented Aug 7, 2023

@Nishant0928 Nishant0928 requested a review from a team as a code owner August 7, 2023 07:14
@rakeshkumar1019 rakeshkumar1019 force-pushed the feat-ELEMENTS-1652-prevent-replacing-and-removing-an-attachment-under-retention-3.0.x branch from d11979b to 1545cc8 Compare August 7, 2023 07:18
@Nishant0928 Nishant0928 changed the title ELEMENTS-1652: prevent replacing and removing an attachment under ret… ELEMENTS-1652-BACKPORT: prevent replacing and removing an attachment under ret… Aug 9, 2023
@Nishant0928 Nishant0928 changed the title ELEMENTS-1652-BACKPORT: prevent replacing and removing an attachment under ret… ELEMENTS-1652-BACKPORT: prevent replacing and removing an attachment under retention Aug 9, 2023
@rakeshkumar1019 rakeshkumar1019 force-pushed the feat-ELEMENTS-1652-prevent-replacing-and-removing-an-attachment-under-retention-3.0.x branch 5 times, most recently from ec55f35 to 04d7b80 Compare August 10, 2023 05:45
@rakeshkumar1019 rakeshkumar1019 force-pushed the feat-ELEMENTS-1652-prevent-replacing-and-removing-an-attachment-under-retention-3.0.x branch from 04d7b80 to d1d3c9b Compare August 10, 2023 05:53
@Nishant0928 Nishant0928 merged commit 88455b9 into maintenance-3.0.x Aug 10, 2023
6 checks passed
@Nishant0928 Nishant0928 deleted the feat-ELEMENTS-1652-prevent-replacing-and-removing-an-attachment-under-retention-3.0.x branch August 10, 2023 15:17
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.

4 participants