[MGNLRES-253] Add recursive activation for resources app Created: 15/Jan/16 Updated: 29/Mar/22 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | app |
| Affects Version/s: | 2.4.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Tu Bo Xuan | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Team: |
| Description |
|
By default, we are not providing recursive activation for content under resources app. It will cost bit of time for user to re-publish all content after migration to re-synchronize data between author & public instances. I would suggest to add publish recursively action as default action. |