[MAGNOLIA-7774] Record parent, previous and succeeding sibling uuids under system node when versioning content Created: 15/Apr/20 Updated: 19/Jul/22 Resolved: 19/Jul/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: | |
| Epic Link: | Order of nodes after publishing |
| Story Points: | 2 |
| Description |
RationaleRecording such information can help us to improve resolution of correct order info when publishing content to public instances when nodes have been reordered in a subtree. This info can be also useful as well when restoring previous version of the content that has been moved to different sub-graph since we have all the information we need about it's previous location. Expected resultVersioned node has 3 new properties saved under system node:
This ticket might be a prequisite for |
| Comments |
| Comment by David Lopez [ 19/Jul/22 ] |
|
Critical issues relevant for customers has been fixed. Remaining topics won't be done. |