[ANALYTICS-51] DashboardComposer should react to Registry changes Created: 27/Mar/19 Updated: 11/Jun/20 Resolved: 11/Apr/19 |
|
| Status: | Closed |
| Project: | Analytics |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Nguyen Phung Chi |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 2d 0.5h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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)
|
||||||||||||
| Epic Link: | Analytics backend | ||||||||||||
| Sprint: | Add-Ons 9 | ||||||||||||
| Story Points: | 3 | ||||||||||||
| Description |
|
Same as we did in ecommerce project, when there is a change in the dashboardDefinition DashboardComposer should capture this and react to this change. Easiest way to achieve this is to ditch the existing dashboard and initialise a new one.
Acceptance Criteria:
Very similar to: https://jira.magnolia-cms.com/browse/ECOMMERCE-88 |