[MGNLACTIVATION-67] Same name siblings Created: 10/Aug/10  Updated: 28/Aug/15  Resolved: 28/Aug/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Philipp Bärfuss
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2704 activation: support activation of sam... Closed
is related to MAGNOLIA-2173 Moving / rename a page on author sho... 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's a quite special use case and I guess the bug is in place since MAGNOLIA-2173:

  • add new page a and activate it
  • copy the page
  • rename the original a to a1
  • rename the copy to former a and activate it

=> so far so good, but now repeat it once again

  • activate a1
  • rename a1 to a12
  • rename a to a1 and activate it

=> a1 should be duplicated on Public instance now



 Comments   
Comment by Jan Haderka [ 28/Aug/15 ]

Same name siblings are not supported.

Generated at Sun Feb 11 22:59:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.