nmenere Atlassian Team

Yes, Only a general admin can set the actor to another user or dynamic user, e.g. person who triggered the event. This is done for security reasons. Project admins can only set the actor to the automation user or themselves. Cheers, Nick

Actually, this isn't quite true. We "just" rolled out "Run as a user" in Jira Cloud last week. If you are a admin, you will be able to set the actor to anyone, otherwise you can only set it to the Automation User or yourself. Hope that is what you are after. Cheers, Nick [Atlassian - Automation Group Product Manager]

Hi @Prasad Rajassekaran , This community space is for the Automation capabilities within Jira. You may have better luck contacting Zephyr or trying another space. Cheers, Nick [Atlassian - Automation Group Product Manager]

Hey Sue, we have recently done a bunch of work around supporting multiple fields with the same name. Would love to hear exactly what you are trying to do and see some screenshots of your rule. If we've missed a common use-case I'd love for us to hear about it. Cheers, Nick

Hi Erik, Although there isn't native UI support for cascading selects, you can do it using the method Andreas outlined in the linked post. But, yes - it is confusing with multiple automation options atm. Cheers, Nick

So the JQL can use any smart values that are available. We have some pretty comprehensive docs regarding smart values - https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/ Hope that helps.

Hi Erik, Looks like you are using the old Automation engine in JSD. This engine is being deprecated and we are pushing the engine we acquired with Automation for Jira. In the Navigation bar, it should be right underneath it. Then you can use the method Andreas lays out here to set Cascading Select fields…

Unfortunately this is a Cloud only feature with no plan to migrate to the Server.

@Bill Sheboy was close on this, a rule like the following should work: * Trigger: sub-task updated (you may want to make this more specific) * Condition: issue type is sub-task * Branch: for jql: key = {{issue.parent.Epic Link}}* Action: the action you want to take This will edit the Epic of the parent. Hope that is what…

Hi Mark, Did you get this working? Screens wont affect whether transitions as fields aren't required (except Resolution when used). Is this a next-gen project in Cloud? We have recently made this a lot easier to specify Statuses and no longer show duplicate names. A screen shot of your rule will help see what is going on.…

Hi, In Jira Cloud we have recently introduced a "Lookup issues" action that allows you to lookup issues via JQL and then reference them later in the rule as a smart-value. With this you could have a rule: * When issue created * Branch on Epic* Lookup issues where jql: "Epic link" = "{{issue.key}}" and statusCategory = new…

Hey @Erik Boneschansker What are you referring to when you say "categorie"? Is that a customfield or maybe a translated field? A screenshot of your rule and maybe the issue fields you want to copy will help us figure this out. Cheers, Nick

Hi @Manjunath Reddy , is this Jira Automation related or are you looking to manually integrate with Jira and looking for a REST call. If so, as usual, @Nic Brough -Adaptavist- is right. Cheers, Nick

@Patrick Roos we send our web requests through Atlassian web proxy so we fall into the ip ranges specified by Atlassian. The ranges can be found at: https://ip-ranges.atlassian.com/ Hope that helps. Cheers, Nick

Unfortunately @Jack Brickey is right and means this use case cannot be supported. It is only after the issue has been fully transitioned as in a new state that we receive the "Issue transitioned event" and kick off the appropriate rules. I have seen some customers transition the issue back to the previous state if a…

Thanks Maxime, Looking into this, it is a bit confusing (I think due to backwards compatibility) - https://confluence.atlassian.com/advancedroadmapscloud/showing-advanced-roadmaps-custom-fields-in-jira-998651396.html In the example above what was the relationship of the 3 issues that are listed? Was the hierarchy between…

Hi Maxime, I don't think "parent" is the right thing to reference here. In order to understand what info is available can you add a "Debug action" with the following: Parent: {{issue.parent.key}} Link: {{issue.Parent Link}} Run the rule and post the audit log here. Cheers, Nick

Before I dig into this more, can I confirm that you mean that the rule didn't get triggered when you created an issue from Advanced Roadmaps. Sorry to pedantic but need to know exactly what it is before I go to the dev team with this. Cheers, Nick

Hi Alex, Is this being done on issue create? Sometimes when we receive the event, the relationship hasn't been established yet, so we can't find the Epic. Cheers, Nick

Hi Maxime, I know of one limitation with portfolio/Advanced Roadmaps around our support for "Parent Link" but if the trigger is for Issue Create then it should work. Are you able to post a screenshot of your rule to see exactly what it is? Cheers, Nick

Hi @Taranjeet Singh , The native version of Automation in Jira Cloud is the old full/Pro version. All customers have access to unlimited project rule executions and depending on your Edition (Free, Standard or Premium) will have limited access to global/multi-project rules. In regards to our Server and DC offerings, we are…

Hey @Dave Mathijs , The Jira Service Desk automation engine (the one that says "Automation") will be retired over time so there will be one all-powerful automation engine that works seamlessly across projects and products. In the meantime, you can continue to use both. Right now there are a few features missing from the…

Hi Lourdes, You are close but you need to tweak it a little: * When: Issue transitioned * For all linked issues* If issue type = Story * If all linked Issues match: status in ("done", "Reject") * Then transition issue to Done Hope that solves your case. Cheers, Nick Menere [Atlassian] Group Product Manager Automation