Role Migration

As part of the UX overhaul, “Roles” have been renamed to “Tasks”, and the names of the roles have been updated to sound more task-like.

If you modified any of the default roles but did not rename then, then they will renamed to the new task names. In addition, the role’s individually-securable permissions (formerly, “tasks”) will be reset to the new, default definitions.

If you don’t want this to happen upon upgrade, then just rename your role to anything other than the default role or task name.

Custom Extensions

Though it is rare, custom extensions referencing the SecuredTask enumeration must be modified and rebuilt to reference a new task. Consult the full list below to see which new tasks may be appropriate for your use case.

Full Task Conversion List

Former “roles” that contained the tasks on the left will automatically be updated to include the new tasks on the right.

* 2 tasks were removed altogether:

• Events_ManageOwnNotifiers – all users should be able to manage their own notifications
• Variables_CreateOrUpdateVariables – variables should be controlled by privileges depending on the scope of the variable, i.e. Release variables with Releases_Manage and Application-level variables with Applications_Manage