Mark Chaimungkalanont Atlassian Team

If you want to do something on the child issues when the parent issue is updated, you could extend your rule and add an "Issue branch" on all linked issues when the issue is updated. That way, you can add actions on the child issues when the parent issue is updated

As a variation on what Bill suggested, could you use the "Scheduled trigger"? That allows you to specify a JQL and will run the rule once for each matching issue, so you can send an email for each matching issue

You should be able to set the Resolution field in your transition action, so hopefully that would fix up your queue problem

Hey there Peter, Sorry a bit late in here but the format for this would be: {{if(webhookData.fields.customfield_11356.value.isNotEmpty(), webhookData.fields.customfield_11356.value, "None selected")}} You might need to play around with webhookData.fields.customfield_11356.value.isNotEmpty() for it to return true / false as…

Thanks for reporting it folks, we'll try and get to the bottom of this

Round robin assignment uses the round robin assignment within the component only, so if you have multiple assign actions, they will all have independent round robin assignments. That might be the issue here?

If you're not seeing a screen when you're transitioning your issues manually, your transition probably doesn't have a screen associated with it. A simpler way would be to remove the "Reporter" field from your Automation rule's transition action. (from the screenshot, where you're assigning it to Blair). Then add a new…

You should be able to check for in a particular role using the user condition. For the field changes, you should be able to access the {{changelog}} object to get the changed values. e.g. SUmmary changed from {{changelog.summary.fromString}} to {{changelog.summary.toString}} Hope that helps!

Unfortunately updating the Parent Link field with Automation isn't supported at the moment. There's a ticket tracking this at https://codebarrel.atlassian.net/browse/AUT-1779

You should be able to use the "Related issues" branch and "Manage Watchers" action with the smart value: {{triggerIssue.watchers}} You can loop over whatever issue you can match with a JQL (the above example will loop over all stories of an Epic) You can then us the add watchers action and the smart value from the trigger…

I think those links are classic "remote links" which Automation unfortunately don't currently support https://codebarrel.atlassian.net/browse/AUT-176

If you need to run Automation rules against multiple issues that matches a JQL, you can use the JQL Scheduled Trigger and supply the JQL to that rule. You can then remove the labels on all issues that match the JQL. There's a handy "Run rule" button on the top right of the scheduled rule so you can run it more easily

Unfortunately, this is by design that project admins can only act on issues within their projects. Only a global admin can set up rules the work across multiple projects

The rule config you have in the last screenshot looks correct from a syntax POV, but not sure if the logic is 100% correct at the moment, the "Related issues" conditions will only match true if *all the stories in the Epic* either don't have a due date, or the due date is < than the triggering issue. Is this the logic that…

If your Agents are in Jira Groups, you can use Automation for Jira to send emails to that particular group

You should be able to use the related issues / issue branches feature with a JQL. The JQL search could then find the "siblings" tickets and the edit the assignee for these e.g. a JQL with: parent = {{issue.parent.key}} You'll probably need to add more conditions here (check that it's a subtask etc) but ho[efully should be…

Thanks for the feedback! I've linked this feedback to https://codebarrel.atlassian.net/browse/AUT-1261 and that'll count as a vote for this issue

Hey there Christopher, Unfortunately not, no. If you know the issues you want to run the rule against and it can be found using a JQL, you can chang the trigger to a scheduled trigger temporarily and then there's a button on the top right to run the rule manually. Cheers, Mark C

Specifically you can't _move_ an issue using Automation but you can clone the issue to the new project and the close / delete the original issue using Automation.

Hey there Luiz-F! Yes that's a known bug. I've llinked the bug report here: https://codebarrel.atlassian.net/browse/AUT-2119 There's no way to workaround this for the moment, unfortunately. Cheers, Mark C

Hey there, I think you should be able to use: {{rule.actor}} Hope that helps! Cheers, Mark C 

Yeah the only way around this limitation (issue linked at https://codebarrel.atlassian.net/browse/AUT-1617) is to set some sort of flag (either a field or a status) on the issue that's on the Board A. Then have a different rule that listens of that trigger, which then loops over the related issues. You'll need to set the…

Hey there Arno, Thanks for the feedback, it's not possible to create branches through Automation at the moment. I've raised a ticket to track this at https://codebarrel.atlassian.net/browse/AUT-2122 Cheers, Mark C

Yep Moga has the solution here. To get the account id, you should be able to use: {{#changelog.assignee}}{{from}}{{/}}

I think you'd use a ticket to represent a release like Jack suggested with addition of Jira Automation on top (https://www.atlassian.com/software/jira/features/automation) If you had: * Issue type called "Release" * Custom fields to track all your dates* "Release due date" * "Verification due date" etc * Custom fields to…

Maybe there are some line breaks or spaces in your description? it's weird that the JQL search would show it up as well

You should be able to use {{issue.Environment.value}} without the quotes. Quotes are only required when there are special characters (like another . ) in the name of the field

You can set up an automation rule to monitor changes on the cascading select field and then set the value of the URL field (or even a text field to the child value of the cascading select list You can do this with: {{issue.Cascading select.child.value}} replacing "Cascading select" with the name of your custom field 

Hey there Ayelet You should be able to use this format to display fields only when there is a value. The example below is for a field called "Select" {{#issue.Select}} Select: {{.}} {{/issue.Select}} You can use the same patterns for multiple different fields to only show the labels when you need to Hope that helps! 

Here there Lara, Project Admin has always been a Pro only feature. In Lite, it's possible to turn on the Pro-trial where you get full access to the app, so maybe you could access it while Pro-trail was occurring (and now it's expired)…