[LIVECOPY-313] Protecting single fields within a composite field is not possible Created: 20/Apr/22  Updated: 21/Apr/22  Resolved: 21/Apr/22

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.2.8
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Tobias Alsema Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive demo.zip     PNG File image-2022-04-20-17-27-38-681.png    
Issue Links:
duplicate
duplicates LIVECOPY-159 Fields under composite/switchable/mul... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It is currently not possible to protect a single field in a composite field.

If the composite is selected to be protected, it is not possible to unprotect the composite.

The UI does not show if a composite is protected.

If a field has the same name as a field in a composite, the UI show the protection button twice, but both are for the field on "root".

e.g. →field & →composite→ field

 

I have attached a basic demo that showcases the issue



 Comments   
Comment by Laura Delnevo [ 21/Apr/22 ]

I am closing this ticket as it duplicates LIVECOPY-159. talsema I have added you as a Watcher to LIVECOPY-159 so that you'll be able to follow the progress on this issue from there. I hope this works for you // cc miruela for awareness

Generated at Mon Feb 12 02:27:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.