Kevin Bui Atlassian Team

Hi @Anthony Ha - this isn't something available out-of-the-box in Jira automation. You might be able to accomplish it using custom workflow post functions (mentioned in another Community question here) but I can't verify if this works or not.

Hey folks! For anyone following this page - we've decided to roll back the release of this feature. Please see the announcement banner at the top of the article. Thank you for your patience as we continue working on this!

@Sarmila Sivaraja Usually if the Add watchers option is missing, it's because you don't have the Manage watchers permission - I recommend reaching out to an admin and ask them to check for you. Hope that helps!

Hey folks! I handle the documentation and in-product content for Atlassian Automation. Just wanted to pop in and clear the air around what happened with these sprint actions. Long story short, this content was published by mistake. Some time ago, we were working on sprint-related actions for Jira Cloud Automation - Create…

Hi everyone! Thank you all for your questions and comments. While I can't answer all of them right now, I can tell you that the product team is looking at all of the comments on this page, and we'll be sending out a larger response soon. In the meantime, I wanted to clarify how rules that span across multiple…

@Rudy Holtkamp - Hi Rudy! We won’t be providing any options for purchasing extra automation runs. I can, however, confirm that the following actions won’t count towards your usage: * Log action * Create lookup table * Create variable I’ve updated the FAQ section with this information. @Mauricio Heberle - Hi Mauricio! Your…

Hi @Bill Sheboy - Great hearing from you again as always. The types of fields available are: * Short text * Paragraph * Dropdown * Number * Checkbox

Hi @ChristopherChilds, thanks so much for your question! My name is Kevin, and I'm responsible for maintaining the Jira Cloud automation documentation. As @Nic Brough -Adaptavist- said, the status definitions aren't in the docs. However, we do define them in product on the Audit log screen: Just wondering if there was…

Hi @OMOTOMILOLA AMUSHAN, On your board, go to Reports > Velocity Chart. The data you see there will be based on your board and its filter.

Hi @Steph Sjostrom - The Create branch in GitLab action does not support self-hosted instances.

Hi @Julia Foden, thanks for your suggestions! Returning the link to the created page is already possible, using the smart value {{createdPage.url}}. So in your example, you'd say Hey @user, here's your page {{createdPage.url}} If multiple pages have been created (i.e. your rule uses the action more than once) you can also…

Hello again @Przemek - sorry for the late response! If I'm understanding you correctly, the rule you want is When issue transitions -> Transition the issue's subtasks too. If so, you can accomplish that with the following: * Trigger: Issue transitioned * Branch: Related issues > Subtasks Here's a screenshot for reference:…

Hi @Sonal Kartikeya - I tried this myself, and it seemed to work okay. This was the rule I used configuration I used: I also had the Multiple projects scope selected, as you said. If you check the audit log for the rule, does it say the rule executes?

Hi Muru, The 255 character limit is a Jira-wide restriction, so unfortunately we can't really work around it. However, you can truncate it to 255 characters using the smart value {{issue.summary.abbreviate(255)}}. For example, if your issue summary was Hello world, then {{issue.summary.abbreviate(8)}} would return Hello…

Hi @Przemek , You can accomplish what you've described in two steps: * Link the two subtasks together (you could even create an automation rule to do this) using a specific link type that you would use just for this scenario, and * Create an automation rule to transition your subtask. The rule would have this general…

Hi @Bill Sheboy - Love the idea. I'm not sure if our docs platform is capable of what you're describing, but I can look into ways of including Community content on the landing page; even if it's a list of articles populated manually.

Hi @Pierangelo Repetti - This is unfortunately not an option, since Jira automation doesn't have any triggers related to users joining a site or project.

Hi @Ibrahim Ghalghay - For your branch to work, you'll need to use one of the Sprint triggers - either Sprint created, Sprint started, or Sprint completed. This is because without a sprint trigger, your Automation rule can't know which sprint to look into. Hope that helps!

Hi @Evrim Demir, The correct syntax is {{#if(equals(issue.Request Type.requestType.name, "IT help"))}} Tech will take care of it. {{/}} and {{#if(equals(issue.Request Type.requestType.name, "Change/Feature Request"))}} Sorry, can't give any estimated completion date yet. {{/}} Our documentation did list the syntax as you…

Hi @Sean Briceland Would you happen to be using GitHub Enterprise? The automation devops triggers (including Pull request merged) can't be used with GitHub Enterprise, so if this is the case the {{pullRequest.destinationBranch.name}} won't return anything. You can find the list of compatible tools on the Automation…

Hi @billy jean , Not sure if I'm understanding you correctly, but I believe {{issue.parent.Epic Link}} can be used to return a parent issue's epic. So perhaps the smart value you're looking for is {{triggerIssue.parent.Epic Link}}. Does that work for you? Cheers, Kevin

Nice work team!

Hi @v_fedorova98 - You can accomplish this with the following rule: * Trigger: Scheduled, with a JQL such as project = "My Project" and issueType = "Epic" and dueDate = now(). * Branch: For Current issue. * Action: Edit issue, select the Due Date field, and enter {{now.plusDays(1)}}. Your rule should look like this: Note…

Hi @Gabriel Viger - I think the easiest way (possibly the only way?) to this would be to use two rules. Rule 1 - Your manual trigger rule, where the epic in Project A is created and linked to the request in Project B. Rule 2 - Triggered when an epic is created; creates stories in project A, and links them to the trigger…

Hi @Marcin Dyszynski - I've been thinking about this a lot, and unfortunately I can't find a way to do this; at least, not in one rule. You could, however, do something similar in two rules. One rule that transitions all issues in the fix version, and then a second rule that triggers when issues are transitioned. For…

Hi @sfullman - If I'm understanding you correctly, what you want is to have a rule that triggers when an epic is created and that epic also has a value in the field Brand. This rule must create a task and add it to this epic. Is this correct? If so, then you should be able to accomplish this with the following: 1. Trigger:…

Hi @Daria H_ I can confirm that what you're looking to do is currently not possible using automation rules in Jira Server. It is, however, possible to do this in Jira Cloud using the Scheduled trigger combined with the Lookup issues action.

Hi @A S , If I'm understanding you correctly, you want to search for issues that have a specific summary, and link them with one another? If so, I believe you can do this using the Lookup issues action, and then have your automation link an issue to each issue in the JQL search using {{lookupissues.key}}.

Hi @Chris Melville, could you please provide more information on what you're trying to do? I'm not sure if this answers your question, but using the Lookup issues action you can enter your JQL query, and then have your automation rule perform actions on those issues (e.g.: Comment on each issue where Development…

Hi @Abby, This was indeed an error, and I've fixed it in our docs. Thanks so much for letting us know! Cheers, Kevin