Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Include Page
Delegated Project Admin 2.0 EAP Notice
Delegated Project Admin 2.0 EAP Notice




Panel
borderColor#efefef
bgColor#efefef

On This Page

Table of Contents
maxLevel3


Video: Guided Path Mode Overview

The following video provides a helpful high-level overview of the user features available in Guided Path mode within Delegated Project Admin Pro for Jira. See the documentation below for additional details.


Widget Connector
width853
urlhttps://www.youtube.com/watch?v=54dyvWmQwHc
height480




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 this configuration has been done, a Delegated Project Administrator will 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 will not see this sidebar option if any of the following are true:

  • You do not have this permission on the current project
  • A Jira Administrator has not delegated any schemes when configuring the app.
  • A Jira Administrator has not delegated any project administration capabilities to your username, any group of which you are a member, or to your role (if applicable) as the Project Lead.



Sidebar (expanded)



Sidebar (collapsed)



Overview

Initially, all projects start off in Guided Path mode. Guided Path mode allows a Delegated Project Administrator to switch a project from one scheme to another.


Image RemovedImage Added


Each type of scheme is represented by a tab on this screen:

  1. Issue Types, which defines the issue types that can be used on issues in the current project.
  2. Fields, which defines the fields that are available to the project and whether each is required or optional.
  3. Screens, which defines the fields available for each issue type when an issue is created, edited or viewed. 
  4. Workflows, which defines the lifecycle of issues for each available issue type.
  5. Notifications, which defines who is notified when a workflow transition or issue operation is performed against an issue in the project.
  6. Permissions, which defines who is permitted to perform certain actions on the project or its issues.

A tab will be shown only when a Jira Administrator has delegated administration of that scheme type to you when the app was configured. One Delegated Project Administrator could see more or fewer tabs than another, if their Delegated Project Admin permissions are different.

Each tab lists the scheme currently in use on the project and contains 2 buttons, represented by and  in the above screen. 

Selecting a different scheme

Clicking the Select Different Scheme button will present a popup similar to what is shown below. 



(warning) When selecting a different Issue Type scheme or Workflow scheme, you will notice additional text in this popup to warn you that the change should only be performed during times of low system usage. Your users could experience a temporary performance slowdown if you attempt these changes while many users are using Jira. This is due to the resource intensive changes Jira must do to accommodate the changes, such as migrating issues from one set of workflow statuses to another.

Click I'm sure - Change the <xxx> Scheme to proceed. Another screen, similar to what is shown below,  will be shown so that you can review other available schemes and identify the one to which you want to switch. The list of available schemes is configurable by your Jira Administrator.



Click Preview to review any of the schemes (including the one currently in use). Once you have determined the one you want the project to start using, click Select.

When you switch to a different Workflow scheme, please note that you will be presented with an additional screen in which you must specify how to map issue statuses from the old workflow to the new one. Once you have completed the mapping, click Migrate to perform the change. (This additional screen does not appear for other types of schemes.)




Once the change has been performed, a confirmation screen will appear. In addition, the change will be recorded in an audit trail for that scheme.



Click Close to dismiss this screen and be returned to the Delegated Project Admin screen.


Viewing History 

While on any tab of the Delegated Admin screen, you can click History to view the audit trail for the current scheme type.



Changes appear in reverse chronological order (most recent changes on top). In most cases, each change will have a Roll back link that you can use to undo a scheme change. Changes can be rolled back in any sequence, and a roll back itself can be undone. In the screen above, if the second Roll back link was clicked, you would see the following screen confirming that the project was reverted to the scheme shown in the Changed From column: "PRM: Project Management Issue Type Scheme."



If you then clicked History again, you would see that the project is now using its original Issue Type scheme.




Viewing Workflows

The Workflows tab has a View Workflow link that allows you to see a visual representation of the workflow that the project is currently using.



If you decide to switch to a different workflow and click Select Different Scheme, you will see the confirmation screen described above where you must click I'm sure - Change the Workflow Scheme to proceed. The next screen contains a Select button as well as a Preview workflows dropdown next to each available workflow scheme. The "Preview workflows" dropdown, allows you to see the name of the workflow associated with each issue type available on the project. Click the name of the workflow within the "Preview workflows" dropdown to see a visual representation of that workflow.



Initial display of screen



Screen after clicking "Preview workflows"


Anchor
priorityScheme
priorityScheme
Priority Scheme


As the priority scheme is introduced in Jira from 7.6 version onwards, we have delegated the editing and switching of the priority schemes to the project admins like any other schemes.

Priority scheme in the guided path

Image Added



Select Priority scheme dialog

Image Added  Image Added


Priority Scheme Preview Dialog

Image Added

Priority Scheme History Dialog

Image Added

Priority Scheme Migration Dialog

When you associate a scheme with the projects from the guided path that were already using a different one, you might be asked to replace obsolete priorities. That's because some issues are using priorities that are not available in the new priority scheme. An issue can't live without a priority, so you need to replace the old with the new.

Image Added

When you click on the Migrate button, Issues in the project will be mapped to the new priorities and in the completion dialog, the number of issues migrated will be shown.

Priority Scheme Completion Dialog

Image Added


Entering 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. Clicking this button places the project into Self-Service mode.

More information about working in Self-Service mode can be found in Using Self-Service Mode - 2.0.