[LIVECOPY-264] Protect Fields set drop status of whole component Created: 14/Jun/21 Updated: 28/Jul/21 Resolved: 28/Jul/21 |
|
| Status: | Closed |
| Project: | Live Copy |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Marvin Kerkhoff | Assignee: | Julie Legendre |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | VN-Analysis, maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: | |
| Epic Link: | Live Copy maintenance |
| Sprint: | Content Mngmt 08 |
| Story Points: | 5 |
| Description |
| Comments |
| Comment by Quach Hao Thien [ 16/Jul/21 ] |
|
Hi marvink2, as I couldn't reproduce the issue, I realize that this is maybe a UX problem. This is the state of component which is Disable updates from master, and yes, the Component node is flag with liveCopyReferenceDropped = true
and this is the state of component which has fields were being protected, and only the propertiesToIgnore was set within an array of field names
Both have the same icon, but different in bar-color, that maybe the reason leading to confusion. Could you help to verify again? Thanks |
| Comment by Laura Delnevo [ 28/Jul/21 ] |
|
Hi marvink2 ( cc miruela) following the feedback from the dev team, we have updated the documentation in order to better explain how the UI status matches the LC behavior. We believe that this is the correct and expected behavior, as we could not replicate the issue reported.
Marvin, please feel free to add a comment and re-open the issue if needed. I will be watching for any follow-up comments.
|