Sam Harding Atlassian Team

Hi @Mateusz Przybyłek One way to achieve this would be to specify the sprint in the 'Addition Fields' JSON in the 'More Options' section. Here you can specify the exact sprint using its id. It would look like this: More information on finding out your sprint id can be found…

Hi @thrilos07 It seems like there might be a problem with the issue type checks here. Can you confirm what the audit log is saying when the rule executes? If I am understanding your situation correctly, you are wanting to fire the rule off when a sub-task of a bug is transitioned to "Done", and then check if the parent…

@felix.weber Hi Felix, We don't host too much information about regex ourselves, as we defer to the broader internet community for documentation and information about regular expressions (such as the oracle documentation you mentioned above). I definitely agree, the documentation can be hard to read, and impractical to…

Hi @Kendra Goldblatt Have been looking at your problem, and trying to find a solution for you. You are correct, the issue is the transition vs creation trigger mechanism. I unfortunately do not believe there is a work around here without using multiple rules to achieve what you are doing. I have raised this use case up…

Hi @NguyenDttn Can you check what statuses are available for the issue? Go to <your_url>/rest/api/2/issue/EX-74/transitions, which should show the available statuses for your issue. Is the status you are wanting there?

Hi @Venkata Ramana Kaza John's comment above is how you can access the sprint smart value when using sprint related triggers, so should help you get started with using sprint related automation rules. Specifically with lookup issues, the sprint field is not supported on lookup issues smart values. This would be the reason…

Hi @Asif Salam Ganesh's answer is correct, there is no functionality to mention groups in JIRA (without using plugins). There is the ability to mention teams, but this works as a macro for mentioning all the individual users in a team. To replicate this in Automation, you would need to mention each team member individually…

Hi Richard, Jack's answer is correct, I believe the confusion here may be around when the (new) automation rule is triggered. The trigger happens on the issue being created, not on the email itself, so your rule would be triaging the generated issue, not the incoming email. If it is the case that there are conflicting…

@Ilidio Faria the lookup issues JQL search string is issue in linkedIssues({{issue.key}}, "relates to") and status != "done" Then the advanced compare condition is {{lookupIssues.size}} equals 0

Hi @Ilidio Faria A way to do this would be to use lookup issues, to see if there are any issues related to the user story which have their status something other than "done". If there are none, then you can transition the story to "done". The rule configuration would be: - When issue transitions to done - For any issue…

Hi, Unfortunately, this is not something that Automation for Jira supports. Whilst you could theoretically use outgoing webhook requests to do this, you would need to configure the rule to store the relevant credentials to authenticate the request in your rule configuration, as we don't provide the functionality to make…

Hi, A way to do this would be to utilise the Lookup Issues action: First lookup the number of total issues in the epic with this JQL: "Epic link" = "YOUR EPIC NAME" The epic name here can be a lookup to the triggering issue's epic, by using {{issue.epic}}. Then you need to save the number of these to a Create Variable…

Hi, You can link multiple issues when creating a new issue by using the 'More Options' drop down on the issue create component. Here, add a json payload with the issue links, following the style outlined here: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/ For you case, the Issue 2 can…

Hi, I'm not completely certain of your use case, but if you are wanting to set the 'Original Estimate' value on an issue, that can be done in 'Edit Issue' action, by selecting the 'Original Estimate' field in the drop down: The format it takes is a number followed by a unit character (for example, 2 days is 2d, 3 weeks 3w…

Hi Eric, Thank you for your patience waiting on an answer for your problem. We have been looking into it, and trying to find a solution for your use case. Unfortunately, the current implementation of custom variables only allows for storing of values as strings. So 'newIndex' in your rule is always evaluated as a string,…

Hi Amanda, Glad that it worked for you. Unfortunately, I could not find specific documentation discussing this functionality, as it is not a common use case that we have come across, needing to perform string operations on a select field value. To work this out I looked directly at the source code and performed some tests…

Hi Amanda, It is possible to do what you are wanting using single select fields, and your current solution is very close to working. To get the string value of a select field, you need to use: {{issue.customfield_10055.getValue.charAt(0)}} The `getValue` is required to get the select's string value, and then the string…

Hi @Daniel Martins Sorry, but I do not think this isn't currently possible using Automation for Jira. Whilst calculating the difference between two fields is possible, performing an action, such as creating a new subtask, a number of times based on that result is not.

Hi Elizabeth, You can do this using an "Incoming webhook" automation trigger. https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#Automationtriggers-Incomingwebhook By creating an automation rule with an incoming webhook trigger, you will be given a url which you can send data to your Automation for…

Hi, Unfortunately this currently is not available, but is something we are looking at adding very soon. Once the work log field is available on lookup issues (see https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues for the current list of available fields), then you…

Hi, The reason this is happening is due to the trigger configuration. The scheduled trigger is using JQL to find issues which match that criteria (project = SH and status = "In review" etc). For every issue that this JQL finds, it will execute the rule, so therefore when it finds 19 issues which match this criteria, it…

@blemasle Thanks for pointing that out, we'll fix that up. Sorry for confusion caused here! Cheers

Hi @Tom Williams , it looks like there might be a typo in your smart value there, the 'i' in lookupIssues needs the be capitalised, whereas in your comments here it is not. Could you verify if that's also the case in your automation rule configuration? Thanks

Hi @José Blanco Villalba the fields priority and duedate aren't currently included in the supported fields for lookup issues (see https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues for the available fields). As we go forward, we are adding more fields into this list,…

@Tom Williams Hi, you can't use the {{lookupIssues.size}} inside the {{#lookupIssues}}{{/}}, but you can use it outside of the list iterator, so you could include the size in your slack message along the lines of Number of lookup issues: {{lookupIssues.size}} {{#lookupIssues}} {{key}} - {{summary}} {{/}} The inability to…

@blemasle You can use smart values in JQL queries, including the JQL used in lookup issues. So to achieve what you are wanting is a case of using the JQL 'fixVersion = {{version}}' in lookup issues (if you are using a version related trigger), and then your template you are using should be as you are expecting.

Hi, It seems like there is perhaps some configuration issue with the way the incoming webhook is set up on the MS Teams side. That error message 'null or empty eventType' is the response your webhook request receives when trying to communicate with MS Teams. I see there have been some similar issues raised in these…

Hi there! Firstly, I would strongly recommend you delete/edit this post to remove config.properties information from the post, as it contains sensitive information that you do not want shared. Secondly, I do not think this is the right place to post this question, as this is the community for the Automation for Jira. I…

Hi, You can specify which projects a global rule runs against via the global administration (link top right, next to the 'Create Rule' button). Selecting your global rule in the global administration list will present you with a 'Scope' field, like so You can use the drop down to select criteria for which projects to…

Hi, At this time, Automation for Jira doesn't support triggers from confluence events, so it is not possible using Automation for Jira alone. One possibility would be to ask the Script Runner for Confluence community. If you had a script triggered from confluence, you could send a web request to an Automation for Jira…