Bill Sheboy Expert

Hi @Gabesz -- Welcome to the Atlassian Community! You appear to be using Jira Cloud and that article is for Jira Server / Data Center versions. I do not believe there is a similar feature built into Jira Cloud. I suspect there are marketplace apps to add this capability as there is a REST API function to update sprints…

Hi @Fernanda Malcolm It would be easy to "break" the mention syntax (using the replaceAll function) so adding a comment no longer mentions someone, but it seems you want to replace the mentions with the display name of the users. To learn if this is possible, we would need to see your rule and observe how you are copying…

Hi @Vishal There is nothing built in to do this with automation rules, but it is possible using assumptions, and math and date / time functions. For your scenario, you want the working flow time between two date / time values. The assumptions to support that might be: * the work day is 8 am to 5 pm, inclusive * the working…

Hi @Naveen kumar Bhoomanagari (HCL) -- Welcome to the Atlassian Community! The short answer is: no, that is not possible with an automation rule for an unknown number of issues to be cloned. The longer answer is... Automation rule branches which could be on more than one thing (e.g., on JQL, linked issues, etc.) are run in…

That inline test to toggle the other form's visibility failing helps narrow things down a bit, however... I note in the documentation that REST API function is listed as experimental, so I wonder if there are known problems not…

The error with the JQL statement is the field Content Writer should be in quotation marks. I recommend writing and testing that JQL stand-alone first with an issue search. Once the field names and syntax are correct it can be used in the rule.

Greetings! My hypothesis is there may not be a quick "fix" for this with automation rules, as that would allow customers to bypass the licensing model for JPD (which is different from both Jira Cloud and Automation packaging limits). For example, a rule could be triggered to change an Idea issue by a user who is not a…

Depending upon your email tool's formatting, the URL or HTML version of it should work. There is a known issue where the Issue Created trigger can fire so quickly that some issue data may not be available when the rule starts. This can lead to unexpected behavior (like empty fields) or rule errors. The work-around for that…

Hi @Nigel Bogle -- Welcome to the Atlassian Community! As other community posts have described, this symptom seems more related to the different licensing / user permissions model for JPD (as compared to Jira Cloud) than an issue with the Automation for Jira user's access. Specifically, rules viewing data for JPD ideas is…

Hi @Ledith_Harrison To add to the existing fix version values, your edit action will need to use advanced edit with JSON rather than the dropdown field list, to "update" with an "add": https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions The reason is the out-of-the-box option…

Hi @Jason Chayer For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Did you try my updated expression, as I found a mistake in the one you are showing which uses replace() rather than remove() for the array brackets...and removes extra spaces resulting from the join()? {{issues.fixVersions.name.join(",").remove("[").remove("]").replace(", ",",").split(",").distinct}} Did you also see the…

Oops...my bad: in rules, issues must be created before they can be linked. Some adjustments to your rule are needed (shown in italics below), as the first issue's key must be saved for use later with the Create Variable action: * trigger: when vulnerability found... * action: create issue (for the Task) * action: link…

Hi @Hunter1428 and @Kalyan Sattaluri FYI, I am using Jira Cloud, not Data Center, and so cannot test what I suggest. With that out of the way... Too bad your instance does not have the automation version with Lookup Issues, as perhaps there is some differences in behavior with bulk-handling and the {{issues}} smart value.…

Looking at your rule image, you want to link the second created issue (a Story) to the first one (a Task). In this case, you can try linking with "Most Recently Created Issue", as that will refer to the one above the action: the Task. Please try that and let me know how it works for you. Thanks! FYI...to use a smart value…

Hi @Kelvin Po Keng Siong When an automation rule references the other issues linked to the current issue (e.g., the parent) only some of the linked issue's fields are available. If it did not do that, you could imagine that a single issue could yank in tons of data, though subtasks, issue links, etc. To assess the other…

Hi @Peter Loh -- Welcome to the Atlassian Community! I believe you may also enter a smart value (for the relevant issue key) directly in that rule action. Have you tried doing that? If that does not work, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image…

Hi @Move Work Forward As a reminder...When recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Harish What type of project are you using: company-managed or team-managed? You may find this information at the lower-left side of the screen expanding area. And if team-managed, is the AccountManager field a People field added only for that project? If so, there is no emailAddress attribute available for People…

Your rule is using the Issue Created trigger, and that trigger can fire so quickly that some of the issue data may not be available when the rule starts. This may cause expected results, such as missing field data and rule errors. The work-around / fix for this symptom is to always add the Re-fetch Issue action immediately…

To find the fields and smart values supported by rules, please try... Smart values are name, spacing, and case-sensitive. And often the smart value does not match the displayed field name on the issue views. The steps below helps to identify the correct smart value (and custom field id) for fields and their structure…

Hi @Marcus_palm If you are asking if the columns / fields displayed for the linked issues can be configured in the issue view, the answer is "no". Here is a suggestion to add that capability, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-36490 Kind regards, Bill

Hi @Luis Núñez Muñoz For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Laxmi -- Welcome to the Atlassian Community! In addition to the other answers provided, I recommend reviewing this free training and documentation from Atlassian on creating JQL queries. The training includes exercises to help build skills in making queries like you asked about.…

Hi @Sanjivani Wayal Yes, and as you have described, you could set a custom field value based on sending the notification in the rule. However there is no way to know if it was received, as the user could have blocked notifications in Jira, there could be email blocking in their company / tools, etc. Kind regards, Bill

Hi @NazZ Successfully using automation rules requires learning and experimentation. Please consider these things to help do that: * Create a free, test instance of Jira Cloud, and experiment with different rule and project types * When creating rules to experiment, write to the audit log rather than performing…

Hi @Igor Medeiros - Modus Create Rather than posting the same boilerplate text promoting your product for every question which is email-related, even for very old questions, please consider instead: * reading the question asked * explaining how your product could help with the specific need Thanks, and kind regards, Bill

Thanks for clarifying, Lucas. And yes, I understand that level of effort for reporting to management on the specifics of team workflow activity :^) Have you considered building a dashboard (or Confluence page) others can go see and pull when needed, rather than sending a report?

Hi @Michaël BELVAL -- Welcome to the Atlassian Community! Yes, and...to Tanguy's answer: A possible work-around could be to import the field into a different custom field (e.g., Due Date), and then use an automation rule to set the JPD field (using their internal format) and then clear, or ignore, the value in the imported…

That depends upon your rule structure and the source of the task data. For a single issue in the rule, it could be the smart values in {{issue}} or {{triggerIssue}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ Please post an image of your complete rule; that will provide context to help…