that changes – from either mode – can be rolled back by a JIRA administrator or a

Delegated Project Administrator.

A JIRA Administrator can choose to delegate only via Guide Path mode, only Self-Service mode, or both. Please note that your selections on this screen will not be put into effect until you have selected your

Delegated Project Administrators on the Select Who to Empower screen.

Delegated Project Administrator to switch a project from one scheme to another.

The types of schemes supported are:

• Issue Type Schemes, which indicate which Issue Types can be used on a project's issues

• Field Configuration Schemes, which define the fields available on a project's issues and the behavior of those fields (e.g., whether each is optional or required, whether each is hidden or visible, and what options are available in dropdown (aka "Select") lists).
  
• Screen Schemes (aka Issue Type Screen Schemes), which indicates which Screens are used to create, view or edit each Issue Type used within a project
• Notification Schemes, which defines who is notified when certain changes or events occur on an issue.
• Permission Schemes, which defines who can perform various activity on the project and its issues.
• Workflow Schemes, which define the lifecycle of issues in the project.

A JIRA Administrator chooses the desired delegation for each of these types of schemes, including:

• Allowing no delegation (i.e. no schemes of that type are selectable)
• Allowing all existing schemes of that type to be selectable
• Allowing all existing schemes of that type – except for specific ones – to be selectable
• Allowing only specific schemes of that type to be selectable

The JIRA Administrator then chooses which Project Administrators can perform various delegated activities in Guided Path mode. For instance, some Delegated Project Administrators may be able to work with Notification Schemes while others may be able to work with each of the supported schemes.

To switch a project from one scheme to another, the

Delegated Project Administrator can click

the Image Modified icon in the sidebar of the Project screen to open the Delegated Project Admin screen

,

click the tab corresponding to the type of scheme to change, and then click the Select Different Scheme

 button. A list of available schemes is shown based on what the JIRA Administrator indicated to allow, and the

Delegated Project Administrator can select the one that should be applied to the project.

By default,

a project

will be

in Guided Path mode,

unless the ability to enter Self-Service mode has been granted and a Delegated Project Administrator with appropriate delegated capability has opted to enter Self-Service mode.

It is important to note that the mode (Guided Path or Self-Service) is based on the project, while the capabilities of a Delegated Project Administrator while in that mode is based on how the JIRA Administrator has configured the delegation for that individual or the groups to which s/he belongs. The project stays in its mode (Guided Path, by default) until someone deliberately changes it to a different mode. It is possible for a Delegated Project Administrator to be unable to do some things or perhaps anything at all in a project if s/he was not delegated any capability pertinent to that mode.

Delegated Project Administrator to do more granular configuration of a project, beyond what can be done in Guided Path mode. The capability within Self-Service mode can include any or all of the following:

• Self-Service mode: Entering or exiting Self-Service mode

• Process Templates: renaming, cloning or removing Process Templates

• Issue Types: Adding or removing Issue Types

• Fields: Adding or removing a Field from the Create, Edit and View screens, making a Field required or optional, or reordering a Field on the Create/View/Edit screens.

• Workflows: Adding or removing a Workflow step, editing the fields available on a transition screen, or reordering the Fields available on a transition screen.

• Notifications: Adding or removing recipients for a notification

• Permissions: Granting or revoking JIRA project permissions to a user, role, or group.

A Process Template is a set of configuration options

that control the workflows, fields, issue types, and groups that can be applied to a project.

By default,

a project

will be

in Guided Path mode,

unless the ability to enter Self-Service mode

has been granted and a Delegated Project Administrator with the appropriate delegated capability has opted to enter Self-Service mode

.

It is important to note that the mode (Guided Path or Self-Service) is based on the project, while the capabilities of a Delegated Project Administrator while in that mode is based on how the JIRA Administrator has configured the delegation for that individual or the groups to which s/he belongs. The project stays in its mode (Guided Path, by default) until someone deliberately changes it to a different mode. It is possible for a Delegated Project Administrator to be unable to do some things or perhaps anything at all in a project if s/he was not delegated any capability pertinent to that mode.

that control the workflows, fields, issue types, and groups that can be applied to a project. Process Templates are available only in Self-Service mode.

When a project initially enters Self-Service mode, its configuration is analyzed and converted into one or more Process Templates. Multiple Process Templates would be created if:

• The Create/View/Edit screens used on a project vary by Issue Type
• The Fields used on a project vary by Issue Type
• The Workflows vary by Issue Type

The behavior of each Process Template is represented by the sections shown on the Self-Service screen:

1. Issue Types, where Issue Types can be added or removed
2. Fields, where Fields can be added or removed; Fields can be made required or optional; or Fields can be added, removed or reordered from screens used to create, edit or view issues
3. Workflows, where Steps (aka transitions) can be added or removed; Fields can be added or removed from transition screens; or the Workflow used on the project can be switched to another existing Workflow.

Delegated Project Administrators can also rename, clone or remove a Process Template.