Scheme Configuration section

The Scheme Configuration section lists each type of schemes supported by the Delegated Project Admin Pro for JIRA add-on. This includes:

• Permission schemes
• Notification schemes
• Issue Type Screen schemes
• Issue Type schemes
• Workflow schemes
• Field Configuration schemes

Available Schemes

The Available Schemes section in the right panel allows you to select which schemes can be handled by non-JIRA Administrators.

For each scheme type listed above, you can configure which options are available to project administrators or leads (whomever it us delegated to in the Permissions section):

• None - This will disable delegation for this particular scheme. (Default)
• 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.

When "Exclude certain schemes" is selected, the right panel will be expanded to list each existing scheme. Click the Action button () to toggle whether that scheme is hidden (i.e. excluded).

When "Only specific schemes" is selected, the right panel will be expanded to list each existing scheme. Click the Action button () to toggle whether that scheme is shown (i.e. included).

Permissions

The Permissions section in the right panel allows you to choose who can Switch (i.e. change) schemes and Create schemes. The ability to Create schemes is currently available only for Permission schemes and Notification schemes, and this allows users to duplicate ("fork") their current Permission or Notification scheme and then maintain it themselves.

For each scheme type listed above, you can set the permissions to reflect the following:

• None - This will disable delegation for this particular scheme (Default)
• 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.

Settings section

The Settings section contains the Available groups option. For Permission schemes and Notification schemes, this allows the global administrator to indicate who can select groups to be included when these schemes are duplicated and maintained on a project basis.

Available groups

The Available Schemes section in the right panel allows you to select which schemes can be handled by non-JIRA Administrators.

For each scheme type listed above, you can configure which options are available to project administrators or leads (whomever it us delegated to in the Permissions section):

• None - This will disable delegation for this particular scheme. (Default)
• All items - This will allow users to select from all of the relevant schemes in your instance.
• Exclude certain groups - JIRA administrator is able to select which schemes that SHOULD NOT be available for others to select from.
• Only specific groups - JIRA administrator is able to select the specific the schemes that SHOULD be available for others to select from.

When "Exclude certain groups" is selected, the right panel will be expanded to list each existing group. Click the Action button () to toggle whether that group is hidden (i.e. excluded).

When "Only specific groups" is selected, the right panel will be expanded to list each existing group. Click the Action button () to toggle whether that group is shown (i.e. included).

Permissions

The Permissions section in the right panel allows you to choose who can Switch (i.e. change) schemes and Create schemes. The ability to Create schemes is currently available only for Permission schemes and Notification schemes, and this allows users to duplicate ("fork") their current Permission or Notification scheme and then maintain it themselves.

For each scheme type listed above, you can set the permissions to reflect the following:

• None - This will disable the selection of groups for this particular scheme (Default)
• Project Lead only - Only the single user that is designated as the project lead on the project will have access to select groups.
• 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 select groups for this particular scheme.