Jira Image of the Day: Editing Workflows with Extended Project Administration

[#1]

Image 1: Workflow “Edit” button in Jira Data Center

Image 2: “Publish” and “discard” options after workflow changes

Image 3: Workflow used by multiple projects.

Image 4: “Extended project administration” ability is disabled

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management, Jira Core
Deployment Type	Jira Cloud, Jira Server, Jira Data Center

What is shown?

A workflow in Jira Server and Data Center

Visit: Admin > Issues > Workflows
Visit: Admin > Issues > Permission schemes

What can we learn?

In the Jira Image of the Day: Extended Project Administration article, we discussed delegating limited workflow and screen editing abilities to project admins. When “extended project administration” is enabled in a permission scheme, a project-level admin can add statuses that already exist in Jira. They can also add, edit, or remove transitions.

Next, let’s see how that ability impacts workflow editing. Here’s are some different scenarios users may encounter based on their abilities.

In the images above:

• The first image shows the “edit” button at the top right of the workflow. After clicking “edit”, a draft version of the workflow is created.

• In the second image, I added the “pending” global status and one incoming transition. After making workflow changes, the two options are “publish” and “discard”.

• In the third image, the project admin cannot edit the workflow because it is used by multiple issue types in multiple projects.

• In the fourth image, the project admin cannot edit the workflow because the “extended project administration” ability is not enabled in the permission scheme.

As shown in the third and fourth images, the project admin sees a “read only” tag.

---

Back to intro and image list