nmenere Atlassian Team

Unfortunately we don't support this at the moment (and generally copying attachments in general). Technical - When images are added as attachments, then the new issue will actually still be referencing the original image. With embedded images, these have a relative reference and hence if you copy the description with an…

Hi Tyler, Unfortunately we don't have support for this field yet (People field in NextGen projects). This issue is being tracked at: https://codebarrel.atlassian.net/browse/AUT-1651 Cheers, Nick Menere [Head of Product Automation]

"Automation for Jira" is now native functionality in Cloud. We offer basic support for Tempo Account in Edit Issue Action.

I think this may require some debugging - looking at specific examples of issues where this passes and doesn't pass. I'd create a support ticket at https://support.atlassian.com/ and provide as much details of the issues as you can. Cheers, Nick

hi @Gavin , Unfortunately I don't think there is going be way to do this as we haven't implemented support for Remote Issue Links. I also don't think there is an issue property that Confluence sets. Sorry. Cheers, Nick Menere Automation Group Product Manager

Hi @Colin Hunt , Do the projects share a field configuration? What maybe happening is in the 2nd project the Priority field is mandatory but in the first it isn't and therefore can't clone into that project as the Priority is not set. Let me know if that is the problem. Cheers, Nick Menere Automation Group Product Manager

Hi, Have you seen the old Codebarrel blog - https://blog.codebarrel.io/automation-for-jira-now-compatible-with-tempo-accounts-643ed61b86c I'm not a Tempo expert but there is some level of native integration. Cheers, Nick Menere Automation Group Product Manager

Hi @Matt Steadman , Can't think of way to do this if the list is unknown. Even if it is known, the potential complexity of the solution may not be worth it. Cheers, Nick Menere Automation Group Product Manager

Hi @Jeff Condit , You can also put a trusted request capture URL into url field and send the request there. You will see the entire packet it sends. Cheers, Nick Menere Automation Group Product Manager

Hi @Olive Sun The Automation user is a system user - doesn't add to your user count but has a lot of restrictions throughout the product. Can be used in some place but not others. Cheers, Nick Menere Automation Group Product Manager

This is correct, Automation focuses on end user automation rather than admin or config changes. Cheers, Nick Menere Automation Group Product Manager

hi @Abhishek Barnwal , is this to do with Jira Automation and sending out web-requests or just generally trying to access Jira API from another source? Cheers, Nick Menere Automation Group Product Manager

Hi @Iana , Can you try the following and see what it puts in the log: {{#=}}{{#debug}}{{issue.timeestimate}} - {{issue.customfield_12406}}{{/}}{{/}} That should tell us exactly what it is trying to evaluate. Cheers, Nick Menere Automation Group Product Manager

Hi @Raphaël NORYNBERG , The fact that a commit quoting the Jira ticket isn't being picked up suggests that the linking isn't correct. If Jira can't identify that a commit has been made, it wont pass the event onto Jira. Can you double check that GitLab is connected properly and that the project is associated withe right…

Ultimately we want to build a smart-values builder/autocomplete but at the moment we rely on documentation - https://support.atlassian.com/jira-software-cloud/docs/advance-your-rules-with-smart-values/

The reason for documentation is that this way of formatting dates is deprecated. The old way is documented at - https://confluence.atlassian.com/automation/archived-date-functions-993924673.html

Hi Matt, Automations kick in after an event. In this case we wouldn't be able to prevent the transitioning happening. I have seen people use rules to transition the issue back to the previous state if some condition wasn't met but this can be a little awkward. Cheers, Nick

You can create a rule for this like: * Schedule trigger - daily * Lookup issues - unfinished tickets * Send Email:* specify To * reference the the issue count using {{lookupIssues.size}} The missing part is if you had to dynamically lookup the Support person or Project. Cheers, Nick

Hi Colin, Moving an issue from one Issue Type to another is fought with danger and is one of the more complicated things inside of Jira. Changing issue type shouldn't be considered part of a normal workflow. We put a big warning up to help people understand this may cause issues: What may work better for you is to create a…

Hey Peter, I'd love to hear the use-case for this as I can't really think of one. Cheers, Nick Menere Automation Group Product Manager

(Copied answer from - https://community.atlassian.com/t5/Jira-Core-questions/XRAY-Link-defect-directly-with-main-US-instead-of-Test-execution/qaq-p/1635662) I'm not too familiar with the inner workings but as long as the Defect or Use-Story is an issue Automation should be able to fill in fields for you - either hard coded…

Hi Kian, Milliseconds since Epoch was converted over from the old way of formatting dates. Good news is the old way is still there: {{#now}}toMillis{{/}} We are tracking adding it to the new way here: https://codebarrel.atlassian.net/browse/AUT-1915 Hope that helps, Nick

Hi Petr, What issue keys are you trying display? In your example you branching on all cloned issues. Are you then trying to populate the field with all the linked issues of the original issue? If that is the case, you should be able to use something like in the Edit issue action (no need to use advanced):…

@Sneha Kumari I'm not too familiar with the inner workings but as long as the Defect or Use-Story is an issue Automation should be able to fill in fields for you - either hard coded or copied from another linked issue. Typically the rule would look like: * On Defect create * <Some condition> * Edit issue action* Set a…

Hi Guhan, Unfortunately we are actively trying to close the gap from the previous automation engine to the new/current one. One of those gaps is being able to set/edit the Request Type. We are currently tracking this at: https://jira.atlassian.com/browse/JRACLOUD-75020 Cheers, Nick Menere Automation Group Product Manager

Hi @Matt Steadman , I spent an hour trying to come up with a solution around this but it is hard to remove the key from that string and still have it parsed by the link issue component. e.g. using {{triggerIssue.Shipped With Keys.remove(issue.key)}} results in ABC-123, , ABC-234 If we had a "filter" mechanism on lists it…

Hi @Ruslan Rekk (Ploskonos) , Unfortunately there is now way to do this at the moment. You can reference the boards id using: {{sprint.originBoardId}} But there is no way to look up another board for comparison, unless you just wanted to compare the actual id. Cheers, Nick

Hi @Gabor Nagy _Midori_ you have been able to do this in the Server version since the beginning. 

Hi Kelsey. If "Target Start" and "Target End" are custom fields on your issue, they should appear. Are they custom fields (e.g. can you manually edit these through the issue page)? We support all date custom fields. The Advanced/Additional fields functionality requires a very specific syntax (the same as used by the REST…

Hi Richard, You can "Branch" on JQL and you could iterate on that list of issues but you aren't going to be able to use the webhook data to then edit those issues. And you wouldn't be able to identify when there is no corresponding issue. We have a feature request open to iterate over arbitrary objects which would enable…