Actions
Bug #26881
closedGroups disabled at creation when 'validate all change' option is set
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
If we try to create a group with the option Validate all change
set, the group is disabled. Which it is not the case when this option is not set.
Files
Updated by Elaad FURREEDAN about 1 month ago
- Priority changed from N/A to To review
Updated by François ARMAND 17 days ago
- Assignee set to François ARMAND
- Priority changed from To review to 1 (highest)
The main problem is that a group should never be disabled because we don't have an "unable" button.
We should audit what/why can disable groups, and if there is anything that can enable them back.
Updated by François ARMAND 17 days ago
So, first: it is possible to disable/enable group via API, but I don't see any other way to do it, especially no way by UI.
Updated by François ARMAND 17 days ago
Updated by François ARMAND 17 days ago
- Related to User story #24206: We need an option to force validation of change requests added
Updated by François ARMAND 17 days ago
It looks like it was always like that, at least since 2018 and #13396
Updated by François ARMAND 17 days ago
- Related to Architecture #13396: We need to be able to decide what workflow to use based on the change request added
Updated by François ARMAND 16 days ago
- Related to Bug #27041: Missing enable/disable button for groups added
Updated by François ARMAND 3 days ago
- Related to Bug #27127: Missing enable / disable action button for group added
Updated by François ARMAND 3 days ago
- Status changed from In progress to Rejected
Won't fixes, because it's what should happen when "verify all" is set. But we need to be able to enable group in UI, see #27127.
Actions