Bill Sheboy Expert

Hi @Niklas Malmberg The pound sign # is a token to indicate the start of some section, as with an iterator or condition in your example. You may seem more examples of iterators here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples That example also uses smart value,…

Thanks for confirming the rule's transition action does not filter on the specific, named one. (That can be done with the "add regex to distinguish..." option.) What happens in your named transition, "Validation failed"? Please show that one. And if this path of investigation (checking the workflow) does not help...There…

What does your workflow look like for the specific issue type involved? For the Transition Issue action in the rule, did you add a filter on the transition name?

Awesome; I am glad to learn that helped!

Hi @Corinne Guibert Adding to John's request to see the image of your complete rule, we cannot see the issue keys for the audit log you show. What is the scope of your rule: single-project, multiple-project, or global? And, in how many projects are the issues the rule tries to access: one, several, or all projects? What…

Hi @Manchenahalli, Raghunandan -- Welcome to the Atlassian Community! I do not have an answer for you, although there are several open suggestions to add such gadgets for the dashboard: https://jira.atlassian.com/browse/JRACLOUD-83046 https://jira.atlassian.com/browse/JSWCLOUD-13586…

Hi @Tejas Patil This is possible to do within an automation rule, and requires some advanced techniques... One would think smart value, list filtering would work for this scenario: !! THIS DOES NOT WORK !! {{#issue.comments}}{{#if(equals(author.displayName,issue.assignee.displayName))}}{{body}}{{/}}{{/}} The reason it does…

Hi @İclal Aslan First thing, this is a very old thread. I recommend creating a new question, and perhaps linking back to this one, to ensure the maximum number of people see it to offer suggestions. Back to your question... For the time tracking fields which show on issues for Jira Cloud, the time spent does display that…

Hi @Steve Holland It appears you are sending the message body with HTML. Have you tried using the HTML hyperlink format for this? <a href="your URL">your text for the link</a> Kind regards, Bill

Hi @Andrejs Uibo -- Welcome to the Atlassian Community! There is no built-in filtering like that for the velocity chart report. You would need a marketplace app for such features. As a workaround... If your teams' have uniquely named sprints (e.g., Blue Team Sprint 23), the board filters could be adjusted to never show…

Well done! And also...I recommend always adding the Re-fetch Issue action immediately after the Issue Created trigger. That trigger can fire so quickly that the rule may not get all of the issue data yet. As a result, conditions and field actions may not work as expected. The re-fetch will slow down the rule a bit and…

I am glad to learn it is working for you. For future needs, please take a look at the documentation for more advanced searches with JQL. There are quite a few helpful examples in there: https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Are you using a company-managed or a team-managed project? You may find that information in the list of projects, or at the bottom-left of the page expanding area.

To learn more about automation rules, I recommend experimentation, perhaps with a test project! You could create a free Jira Cloud site to experiment with rules, although that will be a bit different than what you see with Server / Data Center version. There is also free training on automation available from…

Hi @Adam Sigel When you used the match() function to extract from the JPD date field format, that results in a text value. Please add a toDate call after that to convert before the use in diff(): Date Diff is: {{now.JiraDate.diff(issue.customfield_10239.match(".*start.*([0-9]{4}-[0-9]+-[0-9]+)").toDate).days.abs}}…

Awesome! Now, let's add the issue list iteration back into your email, adjusting to the formatting you want: {{#issues}} * {{key}} -- {{summary}} -- assigned to {{assignee.displayName}} {{/}}

Awesome; I am glad to learn that helped! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Greetings! I see no way to ask a question for the "community announcements" area, so I'll ask it here :^) Who else is seeing intermittent errors in the notifications list (under the bell at the top-right of these pages)? Symptoms I am seeing for the last week include: * notifications for accepted answers show the date /…

Hi @Eman Khan Have you checked if the subtasks are created by a Jira Automation rule? You could confirm that by looking at the history for one of the created subtasks. In that case, to find and update the rule work with your project admin to make the changes. Kind regards, Bill

Hi @Ronny Birresborn -- Welcome to the Atlassian Community! 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…

Hi @Alexandria (Lexi) Codd First thing, the list of smart values available from the rule editor with the { } is a relatively new feature, and does not include all possible fields / smart values yet. I recommend also checking the documentation or using the how-to article to find the supported smart values / custom fields…

Hi @Ben Wilbers When a variable is created within an automation rule, that only exists within the scope of that rule's execution. It is not available to other rule executions. I believe the only workaround for your scenario would be to store the value, either in a specific issue's custom field (by branching to it) or in a…

Hi @Christian Piermayr Adding to John's suggestions: For date / time adjustments in JQL expressions, a lowercase "m" is for minutes and the uppercase "M" is for months Kind regards, Bill

Hi @alessandro_romolo_e -- Welcome to the Atlassian Community! As you observed, the Sprint field is a list of values, helping to preserve the history of what happened to the issue. You may use smart value, list filtering to get the name of the "active" sprint for the issue using this expression:…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @alessandro_romolo_e -- Welcome to the Atlassian Community! For a company-managed project, the solution for this behavior is to have a separate status for the leftmost column of your board which is different from the backlog. For example: * Backlog* status is "Backlog" * Board* leftmost column status is "To Do",…

Hi @Viacheslav Funtov -- Welcome to the Atlassian Community! There is an active incident for scheduled trigger rules, which you may watch to monitor progress: https://jira-software.status.atlassian.com/incidents/50c77g3fb4y3 And also, I recommend checking the main status page regularly to learn if there incidents happening…

Hi @Sabyasachi Nath -- Welcome to the Atlassian Community! As you appear to be on a Jira Cloud, standard license level, I recommend discussing this need with your Jira Site Admin. They may know of tools / apps your company already has that could help, such as JQL or dashboard addons from the marketplace. Until you check…

Hi @Chris Boys This question is for Server / Data Center version, and whiteboards do not exist in those platforms' Confluence versions. Here is the suggestion to add it: https://jira.atlassian.com/browse/CONFSERVER-83249 And, Confluence Cloud added whiteboards after this question was originally posted. Kind regards, Bill

Hi @Nadege Context is important for automation rule questions. Please post an image of your complete automation rule (in one single continuous image), and images of each individual component: trigger, actions, branches, conditions. If your rule is longer than fits on your browser page, please use a screen capture tool, or…