nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Local post functions?

Chris Nagel

It appears that workflow post functions require global admin access and there's no way I'm going to get that, so I'm wondering if there's a way, as a project admin, to tailor my workflow and add some triggers to, as a first step, add user assignments based on transitions of an issue (e.g., assign to the QA person when issue is moved into one of the QA states)?

I've searched for this capability or equivalent but haven't found it so I created a feature request, but on the off chance that I've missed something, I thought I'd post here.

Accepted answers

Trudy P Claspill

Which type of JIRA hosting are you using - JIRA Server/Data Center or JIRA Cloud?

If in JIRA Cloud, are you using a Company Managed project?

Is your project using a workflow that is assigned only to your project, and not shared with other projects?

For JIRA Server/Data Center and JIRA Cloud Company Managed projects, your JIRA Administrator should be able to assist you with create a workflow that applies to only your project, and modifying that workflow to suit your projects needs (if they are willing). Project Admins do not have permission to modify the workflows in those projects.

In JIRA Cloud, project Admins have permission to modify workflows associated with Team Managed projects, but the functionality is quite a bit different in those types of projects.

Jakob KN

As others have mentioned, you'll need Jira Admin permissions to create post functions.

But, Atlassian recently acquired the add-on Automation for Jira, which is automations that can have various triggers, for example transitions. As far as i remember, it's included in Cloud instances and can be installed for free in server/DC instances.

Automation for Jira is available to Project admins, and you'll most likely be able to resolve whichever needs you have with this, instead of using workflow post functions.

All comments

Rob Horan

Unfortunately, this is not something that a Project Admin can accomplish. Full Jira administrative capabilities would be needed for this.

Trudy P Claspill

Which type of JIRA hosting are you using - JIRA Server/Data Center or JIRA Cloud?

If in JIRA Cloud, are you using a Company Managed project?

Is your project using a workflow that is assigned only to your project, and not shared with other projects?

In JIRA Cloud, project Admins have permission to modify workflows associated with Team Managed projects, but the functionality is quite a bit different in those types of projects.

Jakob KN

As others have mentioned, you'll need Jira Admin permissions to create post functions.

Automation for Jira is available to Project admins, and you'll most likely be able to resolve whichever needs you have with this, instead of using workflow post functions.

Rob Horan

That's assuming they're on Cloud. The hosting type is unknown.

Jakob KN

Correct, if they're not on cloud their Jira Admin have to install the add-on if they don't have it already.

Just checked, and the Automation for Jira unfortunately is only free for Cloud users.
However, if the Jira Admins don't have time or for some reason are unwilling to work with post functions, maybe they'd be open to getting the Automation add-on and hand over some of the responsibilities to the project admins.

Chris Nagel

Apparently my response to Trudy didn't post. I'm pretty sure we're using an on-premise instance. There's a user called "Automation" in a lot of our imported Issues, so maybe that add-on is installed.

Assuming it is, can you give me the detailed steps they'd need to perform to give me access to the ability to automate "assign to user on workflow status x"?

Chris Nagel

Judging from the URL, I think we're using an on-premise instance. However, it looks like there's just no option, even if I'm a project admin?

That's why I filed this Feature Request - automating repetitive tasks should be open to any user that can perform the tasks manually.

Chris Nagel

I did not set your answer as accepted because, while it's strictly true, the curtness of the response goes against the community spirit of helping people find answers to the actual issue, not just the stated terms of the search for an answer.