Overview

A Jira Administrator configures Delegated Project Admin Pro for Jira to indicate what can be delegated and who can perform project administrative actions as a Delegated Project Administrator. Once configured, a Delegated Project Administrator can see the Delegated Project Admin option in the sidebar when viewing a project for which they have project administration rights. The project administration rights are based on the Permission Scheme associated with a project and correspond to the "Administer Project" permission.

You cannot see this sidebar option if:

• You do not have this permission on the current project

• A Jira Administrator has not delegated anything when configuring the app

• A Jira Administrator has not delegated any project administration capabilities to you or any group of which you are a member

• The project delegation is stopped or disabled for the current project using the Stop Delegation option in Advanced Settings

• The project delegation is enabled for only few of the projects using the Enable Delegation option in Advanced Settings

Enter self-service mode

When a project is in Guided Path mode, Delegated Project Administrators who have been given Self-Service ability by a Jira Administrator will see an Enter Self-Service Mode button in the top right corner of the Delegated Project Admin screen.

After clicking Enter Self-Service Mode, the following screen is displayed to warn you of the ramifications of switching to this mode.

Open

Please note that if you (or another Delegated Project Administrator) switches the project to Self-Service mode:

• The project remains in Self-Service mode until a Jira Administrator, or Delegated Project Administrator with the permission to enable/disable Self-Service, deliberately exits Self-Service mode for the project.

• Other Delegated Project Administrators can view the Delegated Project Admin configuration of the project. However, they cannot perform a Self-Service action unless a Jira Administrator has delegated that capability to them.

Overview of self-service mode

By default, a project is in Guided Path mode, unless the ability to enter Self-Service mode has been granted and a Delegated Project Administrator with the appropriate ability has opted to enter Self-Service mode.

Your view depends on what has been delegated to you

Self-Service mode allows Delegated Project Administrators to do more granular configuration of a project, beyond what can be done in Guided Path mode. What you can do while a project is in Self-Service mode depends on what a Jira Administrator delegated to you, your role on the project, and the groups to which you belong. In addition, it is possible that one Delegated Project Administrator has greater or less capability than another because of different roles on the project or group membership.

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. If you have been delegated the ability to work in Guided Path mode but not in Self-Service mode, you can still be able to view a project's configuration if the project is put into Self-Service mode, however you see a warning banner like this at the top of the screen:

Open

What happens when a project is placed into Self-Service mode?

When a project is placed into Self-Service mode, the project's current configuration is analyzed and one or more Process Templates are created to represent that configuration. A Process Template is a collection of schemes that, together, represent the entire behavior of the project. A project consists of multiple Process Templates if it uses:

• One set of Create/View/Edit screens for some Issue Types, and a different set for other Issue Types.

• One set of fields for some Issue Types, and a different set for other Issue Types.

• One Workflow for some Issue Types, and a different one for other Issue Types.

This is what the Delegated Project Admin screen looks like once a project has been placed into Self-Service mode:

Open

The group name of the project (DELPROJ 2/16 in the screenshot) is displayed next to the project name in this page. Hover over this group name to view the other projects that belong with the group. You can also navigate the these project by clicking the respective links.

The various sections of the screen are:

• Process Templates — renaming or removing Process Templates, or creating a new Process Template by copying another

• Issue Types — adding or removing Issue Types that are available to the project via the currently selected Process Template

• Fields — adding or removing a Field from the Create/Edit/View screens, making a Field required or optional, reordering a Field on the Create/View/Edit screens. Fields can be filtered out based on their name or description and field type using the Search option provided in the same section.

• Workflow — adding or removing a Workflow step, editing the fields available on a transition screen, reordering the Fields available on a transition screen, or switching to another workflow

• Project Permissions — granting or revoking Jira project permissions to a user, role, or group

• Project Notifications — adding or removing recipients for a notification that is sent when a workflow transition or issue operation occurs

• Project Priorities — adding or removing priorities that are available for issues in a project

• Actions — allow you to either exit Self-Service mode or join an alternate project group if the Administrator has granted those rights to you

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. 

Each of these is discussed in the succeeding sections.

Connect projects with project groups

Connecting a project with another causes the projects to become a Project Group. At this point, any change done to one project is done to all of the projects in the same project group. In order to create a project group, the user has to have been granted the "Project Group" permission by the Jira administrator. Once a user has selected to enter Self-Service mode, they are then prompted with a series of dialogs asking them if the project should join a project group.

If the user selects to join an existing project group, the system scans the configuration of both of the projects joining and the associated project group. If it identifies any issues that are incompatible with the project group's configuration, a dialog is displayed and the project cannot join the project group:

Open

If the project is able to join the project group, but there are changes that is made to the project due to the various schemes being different (Workflow Schemes, Issue Type Schemes, etc.) a dialog is displayed with the details of the changes:

Open

The user can at this point select not to add the project to the group by clicking on Cancel.