[MAGNOLIA-8317] Bootstrap an entire workspace Created: 22/Feb/22 Updated: 20/Jul/22 Resolved: 25/Mar/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2.17 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Michiel Meeuwissen | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | nucleus | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
[X]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | Nucleus Quality Maintenance |
| Team: |
| Description |
| Comments |
| Comment by Adam Siska [ 14/Mar/22 ] |
|
Discovery completed Unfortunatelly unable to reproduce the issue. Just updating module version or magnolia itself won't lead to any problems. Will need probably more detail for 4th step of reproduction steps or stack trace with exceptions. Little bit more specification of expected behaviour for this case would be also worth as re-bootstraping whole workspace might mean also deletion of all content beforehand. Few additional notes:
|
| Comment by Rabie Hayoun [ 25/Mar/22 ] |
|
We couldn't reproduce it, that why we closing the ticket. |