[PUBLISHING-79] Wrong order of nodes after publishing single page Created: 19/Mar/20  Updated: 29/Mar/22  Resolved: 23/Apr/20

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.1.4
Fix Version/s: 1.0.10, 1.1.5, 1.2.1

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 2
Labels: maintenance
Remaining Estimate: 1.65h
Time Spent: 1d 43m
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-03-19 at 14.29.50.png     PNG File Screenshot 2020-03-19 at 14.30.00.png     PNG File Screenshot 2020-03-19 at 16.58.06.png     PNG File Screenshot 2020-03-19 at 16.58.16.png    
Issue Links:
Cloners
is cloned by PUBLISHING-82 Wrong order of nodes after publishing... Closed
Problem/Incident
is caused by PUBLISHING-52 Wrong order after recursive nodes pub... Closed
causality
dependency
relation
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
Release notes required:
Yes
Date of First Response:
Epic Link: Order of nodes after publishing
Sprint: Maintenance 1, Maintenance 2, Maintenance 3, Maintenance 4
Story Points: 8
Team: Nucleus

 Description   

Steps to reproduce:

  • create page tree
  • publish everything
  • check node order on public instance
  • modify page3, page4, page5 so they have orange status
  • publish page2
  • observe wrong order of nodes on public instace

Meeting minutes 2020-04-06



 Comments   
Comment by Mercedes Iruela [ 19/Mar/20 ]

A different way to reproduce:

  • create page tree
  • publish everything
  • check node order on public instance
  • modify page3, page4, page5 so they have orange status
  • publish child4
  • observe wrong order of nodes on public instace

the issue is also changed if you publish child3. However, it works well for child5.

Comment by Jaroslav Simak [ 23/Apr/20 ]

FOLLOWUP: PUBLISHING-82

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