As a system administrator, I can migrate my custom types from the data module to content apps
(MGNLDATA-201)
|
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.2 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Sprint: | 5.2-rc2 |
| Description |
|
Once generated auto-migration of company dataType is complete, we should also make sure to bootstrap its app configuration for 5.2 fresh installs |
| Comments |
| Comment by Mikaël Geljić [ 06/Nov/13 ] |
|
Updated dialogs |
| Comment by Roman Kovařík [ 08/Nov/13 ] |
|
| Comment by Mikaël Geljić [ 11/Nov/13 ] |
|
You're right, from then on we have to propagate updates in migration to new bootstraps consistently. |
| Comment by Philip Mundt [ 13/Nov/13 ] |
|
App launcher group should be bootstrapped in mgnl-bootstrap, the companyApp app launcher in mgnl-bootstrap-samples. |