When creating a new system service (which is a service not activated in the template used to create the current project; it only concerns MW standalone as of today), this service cannot be activated in project at first activation, even if activate checkbox is checked. This has been wrongly introduced by request #31062 How to test ----------- * Create a new project with a template that does not have the MW standalone activated and has the legacy MW (1.23) activated * In the newly created project does not activate MW 1.23 * Open the service edition modal for MW standalone and submit it without any modifications => The MW standalone service must not be switched to used. * Create a new project with a template that does not have the MW standalone activated and has the legacy MW (1.23) activated * In the newly created project does not activate MW 1.23 * Open the service edition modal for MW standalone, check "Activate" and submit => The MW standalone service must be switched to used. Change-Id: Id3c81ee87b7bd4f9ac55c82445a615e98346e1e0

+3 −4

Author

Yannis ROSSETTO (rossettoy) 2023-02-27 15:29

Committer

Yannis ROSSETTO (rossettoy) 2023-02-27 15:29

Hash 1b9cf2445be03308c163c7b1e4a58cc4eddd5e80

Parent ace25fa589f4a9b38af4121c3d831e4a5e0c4fe6

Reference git #tuleap/stable/1b9cf2445be03308c163c7b1e4a58cc4eddd5e80