[MAGNOLIA-6818] Add/remove/keep mgnl:hasVersion mixin when using import Created: 14/Oct/16  Updated: 31/Oct/16  Resolved: 26/Oct/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6774 Same uuids in multiple workspaces lea... 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:
Sprint: Kromeriz 68
Story Points: 5

 Comments   
Comment by Jan Haderka [ 14/Oct/16 ]

shouldn't that be checked and kept/added/removed on import instead? Depending on whether there's version history for said node or not.

Comment by Jaroslav Simak [ 14/Oct/16 ]

That's good idea .. however i am a little bit worried about bootstrap files - i guess we don't want to have that mixin there?

Comment by Mikaël Geljić [ 14/Oct/16 ]

shouldn't that be checked and kept/added/removed on import instead?

That. Might depend as well upon the import UUID behavior?

Generated at Mon Feb 12 04:18:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.