[MGNLMAIL-90] Changed configuration can't be verified directly Created: 10/Oct/17 Updated: 24/Mar/22 Resolved: 24/Mar/22 |
|
| Status: | Closed |
| Project: | Magnolia Mail Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Michael Mühlebach | Assignee: | Unassigned |
| Resolution: | Inactive | Votes: | 0 |
| 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)
|
| Date of First Response: |
| Description |
| Comments |
| Comment by Milan Divilek [ 26/Oct/17 ] |
|
In my opinion this is not an issue, because "Verify Setup" is intended for stored configuration. It's not meant for checking unsaved configuration from "Mail" subapp. "Verify setup" and "Mail Configuration" are different subapps, they are not different tabs in dialog. So they have no connection and you should consider them as different apps. This is how it works from introducing them. Correct use case in my opinion is
If we want test unsaved configuration, we can add for example test button to "Mail" configuration subapp. |
| Comment by Christopher Zimmermann [ 24/Mar/22 ] |
|
Close as inactive |