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; } } }

No transitions found for user using a global rule to update an idea when an epic is done.

saje_753fpo

I am trying to setup an automation rule following the Atlassian guide found here but to no avail.

Here's what the rule look like.

Screen Shot 2023-08-12 at 3.12.49 PM.png

If the rule actor is set to my user, then the rule works but it will no be able to transition any idea if it runs as Automation for Jira system user. I understand that Automation for Jira is probably not given access to the Product Discovery project but how can we do that as it is a system user and it cannot be added to any group or roles.

Accepted answers

saje_753fpo

Just as a follow up, after escalating a support ticket, it was found out that the Automation for Jira permissions fell out of sync for some reasons and only the Engineering team was able to restore the functionality.

All comments

Trudy P Claspill

Hello @saje

Welcome to the Atlassian community.

In the permission scheme for that project, to whom is the Transition issue permission granted?

Screen Shot 2023-08-12 at 12.40.55 PM.png

I believe the Automation for Jira user falls into the scope of the atlassian-addins-project-access Project Role. Does that role have the Transition issue permission?

Bill Sheboy

Hi @saje -- Welcome to the Atlassian Community!

Adding to Trudy's thoughts...

I also wondered about this scenario as Jira Product Discovery (JPD) moved from beta to general availability because my understanding is a Jira user *must* have Creator or Project Admin permissions to make such changes, and that will be charged for each user account monthly. Non-paid seats can only comment on ideas...unless permission is added to Contributors to create ideas.

And also: you appear to be on a Standard level of Jira Cloud license. That level has a limit of 500 global automation rule executions per month. The rule you have designed may exceed that so please take note. https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Kind regards,
Bill

saje_753fpo

@Trudy P Claspill I also wondered about the permission scheme but Jira Product does not provide the same interface as seen in this screenshot.

Screen Shot 2023-08-12 at 7.54.29 PM.png

@Bill Sheboy Oh! I did not know about the upper limit of 500 global automation rule executions per month. If that limit applies to only them rules that produced an actions then I think we will be fine as we're not gonna close 500 epics per month but otherwise, yeah, we will for sure burst out. This thought make me wonder if it is possible at all to automate this without upgrading to a bigger plan.

Bill Sheboy

If a rule triggers, that counts as an execution. That applies even if the rule does nothing other than be triggered.

saje_753fpo

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud