Global administration
Once the Delegated Administration for JIRA add-on has been installed and valid license supplied, you can access the Global Configuration screen in the JIRA Administration area.
From this screen, you can set permissions for who can change schemes and which schemes can be handled by non-JIRA administrators. This includes:
- Permissions scheme
- Notifications scheme
- Issue Type scheme
- Issue Type Screen schemes
- Workflow scheme
- Field Schemes
Who can you delegate administration to?
For each scheme type listed above, you can set the permissions to reflect the following:
- None - This will disable delegation for this particular scheme
- Project Lead only - Only the single user that is designated as the project lead on the project will have access to configure this scheme.
- Users with Project admin permissions - If somebody has access to the project administration functionality (version, roles and component editing for example) they will have access to configure the relevant scheme.
For permissions and notification schemes, an additional permission type allow users to duplicate their current permission or notification scheme and then maintain it themselves.
Scheme selection
For each scheme type listed above, you can granularly configure what options are available to project administrators or leads (whoever is delegated to):
- None - This will disable delegation for this particular scheme.
- All items - This will allow users to select from all of the relevant schemes in your instance.
- Exclude certain schemes - JIRA administrator is able to select which schemes that SHOULD NOT be available for others to select from.
- Only specific schemes - JIRA administrator is able to select the specific the schemes that SHOULD be available for others to select from.
Available Groups
For permissions and notification schemes, the global administrator can manipulate who can select groups to be included when these are duplicated and maintained on a project basis. The same setting as above are used.
Project administration
Once a user has been given permission to a Delegated Administration component the "Delegated Administration" link is shown on the Project administration page.
Overview
Currently only Permissions and Notifications supports "forking" (maintain their own local version). More will be added in the future.
On the project's "Delegated Administration" screen, each available scheme type is shown with options to Change or Fork the scheme. If a user doesn't have the proper rights for a certain component (or it has been disabled) it is not shown on this page.
For each item a user can select to:
- Change - allows users to switch the scheme to another scheme
- View History - Allows for quick reversion to a previous scheme.
- Fork the scheme (only available for Permissions and Notification schemes) - Clones the scheme and allows for local editing of it.
Duplicating and maintaining Permissions and Notification schemes locally
If a user elects to Fork a permission or notification scheme, they're presented with a dialog for a new name.
Once this has been done a new Edit option appears. From this the user can add permissions or notification targets.
At any point they can revert the forked scheme back to the original. This will then flip it back (if possible) and delete the forked scheme.
