Bugzilla – Activity log for bug 5008: Not clear that tlwebadm changes require a restart of services
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | New Account
- | Log In
- | Forgot Password
Back to bug 5008
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| ossman | 2014-03-04 11:02:16 CET | Target Milestone | --- | Future |
| ossman | 2022-07-07 09:30:23 CEST | See Also | https://www.cendio.com/bugzilla/show_bug.cgi?id=5376, https://www.cendio.com/bugzilla/show_bug.cgi?id=4535 | |
| ossman | 2022-07-07 09:30:54 CEST | See Also | https://www.cendio.com/bugzilla/show_bug.cgi?id=4085 | |
| ossman | 2023-01-17 13:28:22 CET | Summary | Inform users when a service needs to be restarted for a changed setting to take effect | Not clear that tlwebadm changes require a restart of services |
| wilsj | 2024-09-13 09:45:56 CEST | CC | wilsj | |
| tobfa | 2025-04-23 13:07:10 CEST | CC | tobfa | |
| samuel | 2025-05-02 15:52:43 CEST | Acceptance Criteria | , since it poses a risk for potentially unwanted configuration to be pushed into production. SHOULD * Web Admin should add a way to conveniently restart relevant services after a configuration change. COULD * Web Admin could clarify the changes | |
| Target Milestone | LowPrio | 4.19.0 | ||
| Acceptance Criteria | that do not warrant a service restart. MUST * Web Admin must inform the admin which service, if any, needs a restart after a configuration change. * Services must not automatically be restarted after config changes | |||
| CC | samuel | |||
| Assignee | aaron | samuel | ||
| samuel | 2025-05-06 17:09:54 CEST | Acceptance Criteria | that do not warrant a service restart. MUST * Web Admin must inform the admin which service, if any, needs a restart after a configuration change. * Services must not automatically be restarted after config changes, since it poses a risk for potentially unwanted configuration to be pushed into production. SHOULD * Web Admin should add a way to conveniently restart relevant services after a configuration change. COULD * Web Admin could clarify the changes | wanted. COULD * Web Admin could clarify the changes that do not warrant a service restart. MUST * Web Admin must inform the admin which service, if any, needs a restart after a configuration change. * Services must not automatically be restarted after config changes, since it poses a risk for potentially unwanted configuration to be pushed into production. SHOULD * Web Admin should add a way to conveniently restart relevant services after a configuration change. * It should be easy to dismiss the question if |
| samuel | 2025-05-08 17:20:58 CEST | Keywords | relnotes | |
| Status | NEW | RESOLVED | ||
| Resolution | --- | FIXED | ||
| tobfa | 2025-05-09 08:42:23 CEST | Keywords | tobfa_tester | |
| tobfa | 2025-05-09 11:05:57 CEST | Resolution | FIXED | --- |
| Status | RESOLVED | REOPENED | ||
| samuel | 2025-05-09 17:26:16 CEST | Status | REOPENED | RESOLVED |
| Resolution | --- | FIXED | ||
| tobfa | 2025-05-12 13:10:26 CEST | Resolution | FIXED | --- |
| Status | RESOLVED | REOPENED | ||
| samuel | 2025-05-13 12:16:02 CEST | Resolution | --- | FIXED |
| Status | REOPENED | RESOLVED | ||
| tobfa | 2025-05-13 16:26:25 CEST | Status | RESOLVED | CLOSED |
Back to bug 5008