|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14428) Provide group operations f... [email protected] (JIRA)
- [JIRA] (JENKINS-14428) Provide group operati... [email protected] (JIRA)
- [JIRA] (JENKINS-14428) Provide group operati... [email protected] (JIRA)

The string variant worked very well, thank you!
AS for the configuration by views - We do have views and we use them to separate our hundreds of projects to groups, but even if I would want to use it - it will still require me to click through dozens of check boxes if i want to disable the whole group. Therefore "check all"/"uncheck all" still makes a lot of sense to me. What if i need to disable three/four groups??
Our job names are actually including group name (in a format of group+jobname), therefore if I would like to work with one or more groups I will now go to the string slicer, cause it has jobs listed in alphabetic order so i can manage them much easier, but never to "by view" - too many clicks.