[PAGES-1139] Excess areas can break template annotation endpoint Created: 21/Apr/23  Updated: 16/Jun/23  Resolved: 15/Jun/23

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

Type: Bug Priority: Neutral
Reporter: Robert Šiška Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-1140 Implementation Sub-task To Do  
PAGES-1141 Review Sub-task To Do  
PAGES-1142 Pre-Integration QA Sub-task To Do  
PAGES-1143 QA Sub-task To Do  
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: SaaS Post-TPR - DevX
Story Points: 2
Team: DeveloperX
Work Started:

 Description   

Steps to reproduce:

  1. Create a page template with two areas
  2. Open the page and add components into both areas
  3. Remove one of the areas from the template definition
  4. → Template-annotation endpoint fails for this page.

Observed on norsu, check JCR implementation too.



 Comments   
Comment by Christopher Zimmermann [ 15/Jun/23 ]

Addressed in linked SaaS tickert: https://magnolia-cms.atlassian.net/browse/SAAS-61

Generated at Mon Feb 12 06:25:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.