RELEASED: Public: 2012-10-19
New features
Allow non-filterable roles apply to previously filtered roles
-
If a role was marked as filtered, then changed to non-filterable, the role will still be filtered until the filters are saved.
-
Now the filterable state of the role is applied when computing the effective permissions. This means that a role can be toggled non-filterable (view the hidden folders) and toggled back filterable and the folder where the role was filtered (unless modified) will retain the filter
New roles should be filterable by default.
Resolved issues
-
CloudBees Internal Ticket: RM-1490
[RM-1490] If a previously filtered role is now unfilterable, display it as unfiltered.
Visually display implicitly granted permissions.
task.jelly#permission unsuitable for Manage Roles since you need to have this permission on Jenkins, not just a folder.
-
CloudBees Internal Ticket: RM-1468
[RM-1468] New property of a role that prevents it getting filtered
-
Leveraged original code for selecting which roles are filterable so only needs testing of data migration
-
Such testing is a by hand at present as I cannot see a good way to test it automated
-
Also need to ensure that DEV@cloud’s Config implementation is compatible with the new version of this plugin
Javadoc fixes.
cloudbees-license 3.4 seems to make tests reliable.
Tool tips.
Check/uncheck all should not touch $filterable.
Links to inherited groups were broken.