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.
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.
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.
Hello @saje
Welcome to the Atlassian community.
In the permission scheme for that project, to whom is the Transition issue permission granted?
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill I also wondered about the permission scheme but Jira Product does not provide the same interface as seen in this screenshot.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If a rule triggers, that counts as an execution. That applies even if the rule does nothing other than be triggered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I apologize for providing an incorrect answer. I did not make note that you said you are working with the Product Discovery product. I have not worked with that product yet.
I have not found anything yet that specifically talks about the Automation for Jira user and the Product Discovery permissions, nor the "addins" role that is available in Software/Service/Work Management projects.
The demo video from the page you referenced has the rule actor set to Automation for Jira, so you should be able to run the rule with that actor.
I did find a Product Discovery group here in the community. Maybe a post there has the answer, or you might post there to see if somebody there has a conclusive answer.
https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery
Or you could open a support case directly with Atlassian to ask about this:
https://support.atlassian.com/contact/#/
I'm interested to learn the answer to this, so please report back what you learn if you learn something outside of this thread. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Trudy Claspill
I joined the Jira Product Discovery group as per your recommendation and asked the question there.
As for the rule execution limit. I will simply create a new workflow for EPIC with a new status that only EPIC uses. Something like COMPLETED and will use that status as the trigger so that I don't end up firing the rule for every other issues that may use the DONE status.
I truly appreciate the heads up about that @Bill Sheboy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.