Jira Image of the Day: New Delegated Workflow and Layout Permissions in Jira Cloud

[#1]

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management
Deployment Type	Jira Cloud

What is shown?

Workflow and layout announcement banners on the Permission schemes admin page in Jira Cloud.

Visit: Admin > Issues > Permission schemes

What can we learn?

In 2017, Atlassian started empowering project administrators to edit their workflows and screens. By delegating selected editing capabilities, it freed up application administrators to work on more meaningful tasks. For a refresher on extended project administration capabilities in Jira Server and Data Center, see these articles:

• Jira Image of the Day: Extended Project Administration

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

Now, similar concepts are making their way to company-managed projects in Jira Cloud. Open a permission scheme and you’ll now see the following new line items: Manage Issue Layouts and Edit Workflows.

Just like in Server and Data Center, there are safety limitations to the edits users can make. For example, only layouts and workflows that are not used by other projects can be modified. Additionally, users must have administration permissions in the related Jira project.

Trust Warning

In the documentation, Atlassian warns that these capabilities should only be granted to experienced Jira users. “Users with the Edit Workflows permission may be able to affect issues they do not otherwise have access to, as they are able to modify fields in transitions. Users with this permission will be also able to see lists of the following global entities in dropdown boxes when updating [workflow] rules: Events, Screens, Fields, Roles, WebHooks, and Issue Security Levels.”

I’ll add an additional consideration: Only grant these capabilities to users who understand your organization's internal processes, issue lifecycles, and overall Jira customization and maintenance strategies.

---

Back to intro and image list

[Thorsten Letschert _Decadis AG_]

Great insights. And a +1 for your 'Trust Warning' section.

[Tomas Vaicekauskas]

What about changing the workflow status name? It changes for the whole site or just for that project? Because jira admins tends to forget about this until their first mistake :)