Mark Chaimungkalanont Atlassian Team

hhmm interesting question... It's a bit tricky but you can use an * "Advanced branching" branch with {{issue.comments}} with a variable name thisComment * Edit comment action, pick smart value and {{thisComment.id}} this will let you edit all of the comments of an issue I had a quick play and this seems to work! Good luck!

Hey there Kirstof! This isn't possible with native Automation at the moment (see https://codebarrel.atlassian.net/browse/AUT-1083) Your best bet is to try out one of the Marketplace Vendors in the mean time Cheers, Mark C

Not sure if this is what you want but if you only want to edit the field on certain link types, you need to use the "Advanced compare condition" and match on specific link types. {{linkType}} equaks Reuse

Alex, did you try: {{issue.epic.summary}} That should be the correct smart value to use

Unfortunately, controlling the concurrency of rules isn't possible at the moment https://codebarrel.atlassian.net/browse/AUT-517

Unfortunately branching / looping though the "Parent link" field is not yet supported https://codebarrel.atlassian.net/browse/AUT-1779

You could use the lookup issues action to find the issues from the start of the month using the appropriate JQL. See https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues for more usage Note that this is limited to 100 issues being looked up You can sum up various fields like:…

You can use smart values inside an email. For some examples, see https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ If you're looking to use the displayName of a user, you can use a smart value like: {{issue.reporter.displayName}} You can replace reporter with the name of the field you're trying…

Hey there Melissa, You can use the "Scheduled trigger" and using the JQL like status changed BEFORE -60d and status = Closed The trigger will find issues that have been in a status, in the case "Closed" for 60 days. Then you put your conditions and automated actions in the body of the rule Hope that helps! Cheers, Mark C

The TIC-3407 is in a commit message This should automatically link the ticket and if you use the "Build successful" trigger. As far as smart values go, the best way to debug is to add a "log action" and output the smart value to the logs to see the details.…

You should be able to use the Create version action setting the name of the version to a smart value. For smart values that are available check out https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ e.g. {{now.year}}.{{now.weekOfyear}} the number of the release is something that needs to…

The HTML version of the field should contain the table's HTML... I did a test and it looked like: <div class='table-wrap'> <table class='confluenceTable'><tbody> <tr> <th class='confluenceTh'><b>This is a table</b></th> <th class='confluenceTh'> </th> <th class='confluenceTh'> </th> </tr> <tr> <td class='confluenceTd'>New…

Is the field in question a People field in one of the Team managed project types? That field type isn't supported yet, which may explain why it doesn't appear on the list

To work with related issues, it's best to use the the "Related issues branch" and select related issues. In that branch, you can use conditions to reduce down which related issue you need to edit. Then you can update the related issue in the branch, referring to the trigger issue: e.g. You can set the summary to be:…

Can you post a screenshot of what you're setting the Reporter to? It's also a good practice to add a "Log action" before editing reporter with the smart value you're setting in the reporter so you can debug / output it value and see what it's setting.

I guess there're two parts here, first is to match the "SAMPLE USER" and then to use the value of the SAMPLE USER to set the custom field. To parse out the SAMPLE USER, using the .match like you did should work. It's probably a matter to debugging the regex using the audit…

There is a "distinct()" function that you can use, as long as the underlying object is a list. Although, if the actual object aren't Strings underneath, mileage may vary. eg. {{issue.comments.author.distinct)}}

You can get the number of month by doing something like: {{now.monthOfYear}} So you can do something like {{#if(now.monthOfYear.gt(6))}} Second half of year {{/}}

Hey there Josh, You should generally use the status to track if an ticket has a customer response or not. e.g. have a "Waiting for customer" status while the ticket is waiting for a response. Then you can add automations that uses the a JQL to match tickets that have been in this status for more than 3 days e.g. status =…

Unfortunately, Automation doesn't support remote links (links between instances) or copying between instances at the moment. The issue for remote link is being tracked at: https://codebarrel.atlassian.net/browse/AUT-176

You can use smart values in JQL but you'll need to make sure it evaluates to a proper JQL. My advice would be to use the Log Action to try to create you JQL string and then test out the JQL manually to make sure it's valid. e.g you might need to add quotes around the JQL to make it work in some cases e.g. assignee =…

Hey there Simon, To backup Fabian here, the first step is to ensure that your email handler adds a comment rather than creates a new issue. Automation will only work on issue events rather than emails directly. Once you've got your email handler adding comments you can set up your rule to be: * Trigger on Comment *…

Hey there Shakir, Unfortunately, I don't think this would be possible in server. In cloud you'd be able to use: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues And set the assignee to something like {{lookupIssues.get(0).assignee}} Sorry about that! Cheers, Mark C

You could use the smart value .size and the Advanced Compare condition (see https://support.atlassian.com/jira-software-cloud/docs/smart-values-lists/) e.g. have an Advanced condition that checks for: {{issue.My checkbox field name.size}} EQUALS 2 And then in that block set the appropriate labels

Yes unfortunately this isn't possible at the moment and is being tracked at https://codebarrel.atlassian.net/browse/AUT-1264

Can you try adding a "Re-fetch issue" action before the condition? It might be a problem with the timing of when the request type is updated

Hey there, If you use the email address as a smart value in the Assignee field in the Edit issue action, Automation will try to resolve that email to a user (it might not work if they've restricted access to their email) Hope that helps! Cheers, Mark C

Hey there Michael, If you're using cloud you can now loop over smart values as mentioned at https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 You can then use the name of component as a summary of the create issue task like {{component.name}} and the set the…

Yes that maths is correct and you will have 10500. The limits aren't being enforced for Premium trials but you'll continue to be notified when you're approaching the limits

The syntax looks right to me.. The best way to debug this is to actually run the JQL search in Jira itself and see which issues match, that way you can tweak the query without Automation and then once you have the query you want, use that in Automation itself