[PUBLISHING-62] Nodes order is not respected after publishing Created: 16/Aug/19  Updated: 29/Mar/22  Resolved: 06/Sep/19

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.0.7, 1.1.1
Fix Version/s: 1.0.8, 1.1.2

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.25d
Time Spent: 28m
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLACTIVATION-139 Wrong nodes order after publishing Closed
relates to PUBLISHING-52 Wrong order after recursive nodes pub... 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:
Epic Link: Order of nodes after publishing
Sprint: Maintenance & Releases
Story Points: 3
Team: Nucleus

 Description   

Steps to reproduce:

1. Create 4 nodes (names 1-4 and in that order) on the same level, publish them all.
2. Move node 1 between 3 and 4.
3. Move node 2 between 3 and 1.
4. Publish node 2.
5. Publish node 1.
6. See the difference between author and public

 

Note: the order can be fixed by publishing node 3 as well.

 

Most likely there's insufficient ordering info we send during the activation process (only the siblings are included and not the whole structure).


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