[NPMCLI-115] Component availability is messed up under certain conditions Created: 14/Mar/17  Updated: 20/Mar/17  Resolved: 16/Mar/17

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

Type: Bug Priority: Major
Reporter: Iran Campos Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Cursor_and_home_yaml.png    
Issue Links:
relation
is related to NPMCLI-53 Adding availability removes comments ... 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
Sprint: Basel 87
Story Points: 1

 Description   

When you have 2 or more areas with availability in single template (page) and you use the CLI to create new component and add its availability this results in the previous component being placed under the created one.


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