Bill Sheboy Expert

Hi @Sven Müller This does appears to be a new / experimental feature as it is not listed in the last few weeks of Cloud release blogs: https://confluence.atlassian.com/cloud/blog I recommend trying to disable it by: your avatar at the top-right of page > personal settings > disable Jira labs features If that does not help,…

Hi @James Pollard -- Welcome to the Atlassian Community! There are several ways to solve this...depending upon if the information in the email has some unique identifier to join the first request and the later approval. Following the theme of your current approach, your existing automation rule could use the unique…

Hi @Meghana PK -- Welcome to the Atlassian Community! That is theoretically possible with Jira Automation, but only for up to 10 issue in a chain of issues. That limit is because such a rule will need to recursively trigger itself, and there is service limit of 10 such…

Hi @Antonio M_ Ferreira -- Welcome to the Atlassian Community! Just to confirm, you want to contact *all customers* using Slack when the next person in the on-call rotation takes over? What problem are you trying to solve by doing that? That is, "why do this?" When one of your customers creates an issue (e.g., a service…

Hi @Karl Gustafsson -- Welcome to the Atlassian Community! Yes, and...to Marc's suggestions: Perhaps update your audit log write for the user variable to more easily see if there are leading / trailing characters in it, thus preventing the assignment: user: ZZZ{{jiraUser}}ZZZ Kind regards, Bill

Hi @vincenzo.spatafora No, it is not yet possible. For Jira Data Center, the Lookup Issues action only supports a limited number of fields: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-lookupissues-properties There is a suggestion to add the other fields, which…

Well done on that workaround! Another automation approach for such scenarios is more an after-the-fact thing: * remove the workflow validator on the field * create a rule triggered on issue transitioned * detect the empty field with a condition * send a notification / mention to the {{initiator}} * transition the issue…

Hi @Manali Butey As this is a very old thread, please create a new question, perhaps adding a link back to this thread. That will ensure the maximum number of people see it to offer suggestions. When you create your new question, remember to include the following: * what is the problem you are trying to solve; that is,…

Just following up on these questions: What is your Jira Version: Cloud, Server, or Data Center? Did you confirm the field types are date picker? Did you try using the custom field id values rather than the smart values for the field names? For example, with made up ids: {{#lookupIssues}}…

Hi @Dominic Roy Arokiaraj Yes, and...to the suggestions from @Marc -Devoteam- There are many posts in the community for a similar scenario. I recommend searching the posts to find example rules as a starting point, try to build your rule, and then ask for help if it does not work as expected. Successfully using automation…

Hi @Deniz Oğuz - The Starware 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 @nick_pearson -- Welcome to the Atlassian Community! That is the date format used by Jira Product Discovery (JPD), and the values are plain text in automation rules. Thus text functions must be used to extract the value needed (e.g., "start"), and converted using toDate before the diff() can occur. For example:…

Hi @Andreas Söderberg -- Welcome to the Atlassian Community! My apologies in advance for my long response :^) I agree with the insights and suggestions from @Walter Buggenhout and I understand the coordination "priority" problem you are trying to solve for subordinate work that spans teams for delivery at larger scales…

Hi @Csaba Vertessy First thing, to avoid potential rule errors with smart value collisions, I recommend always adding a prefix to variable names, such as varIssueDescription rather than issueDescription. What does the audit log show when you run your rule? (I recommend writing those diagnostic messages to the log rather…

Hi @tatevikalaverdyan Is the rule image you show your current rule, and you want a second rule for the additional scenario of creating a new subtask? If so, what have you tried thus far to solve this need? If you have a rule that is not working as expected, please post an image of that rule and the audit log details; those…

Hi @Aaron Hunt For the scenario you describe, you seem to want this: GIVEN a specific set of Epics WHEN a scheduled time has arrived each day THEN for each child of an Epic which has a specific status and type, add a Label to the child Branches cannot be nested in rules (yet), and as written your rule cannot access the…

Hi @Scarlet -- Welcome to the Atlassian Community! That is possible, and may cause potential rule problems. See the note at the end for details. Let's assume your rule looks like this: * trigger: comment deleted * action: ...some action In the rule details at the top, if you change the Actor to "User who triggered the…

Hi @Abhishek Misra -- Welcome to the Atlassian Community! If your sprints have a standard naming convention, this scenario is possible with automation rules, although it is quite elaborate. For example, if one team's sprints are named "Team Apple Sprint NNN" and "Team Orange Sprint NNN", they could be filtered from the…

Hi @Claudia Riverin When you describe this: The rule is working only if I change status manually but not when my automation is transiting the ticket. Is the rule running and not working as expected, or is the rule not triggering at all? * If the rule is running and not working, please post an image of the audit log details…

Thanks for that information, Mike! Just to confirm, you are using Jira Cloud and not Server or Data Center, correct? What are the types of the custom fields? They seem to be date picker fields, otherwise these would not work with the format() function: {{startDate.format("M/d")}}-{{endDate.format("M/d")}} In that case the…

Hi @Juan Tercero -- Welcome to the Atlassian Community! Are you asking about using the issue URL smart value in an email sent by a Jira Automation rule? If so, please try formatting the URL with an HTML link in the body. For example: <a href="{{issue.url}}">{{issue.key}} - {{issue.summary}}</a> Kind regards, Bill

Hi @Eduardo Please stop posting bot-generated content. For more details, please see the community guidelines: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Thanks, Bill

Hi @Mike.Mikaelian First thing, what problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer better suggestions. Next, and as a short answer: there appear to be field type errors and missing syntax in that iterator expression. Please see details below. The startDate and endDate…

Hi @Alex Short answer: To generate this actual report format you describe, you will need a marketplace app. As a workaround, there are a couple of methods with automation rules for a limited number of epics / child issues. Regarding workarounds... Do you want this in a single email? If so, with out-of-the-box features of…

Hi @Carl Solomon As you have shown your rule, it is triggered on Version Updated. And thus you see the error for the Issue Fields condition because there are no issues in scope. The rule would need to branch to the issues associated to the Fix Version to access them...and then any updates to the Summary may be done. With…

Hi @Carles Capellas -- Welcome to the Atlassian Community! First thing, the Parent field is definitely used in team-managed projects. That is how issues-to-subtasks and epics-to-child issues are linked. Next, there is a known problem for team-managed projects where the workflow validator cannot consistently detect empty /…

Hi @vincenzo.spatafora This seems to be the same / related question as in your other thread: https://community.atlassian.com/t5/Jira-questions/Display-last-n-comments/qaq-p/1832584 Kind regards, Bill

Hi @Bruno Brzozowski If you just noticed this behavior start less than a month ago, and have not changed your locale settings or the query, I recommend working with your Site Admin to contact the Atlassian Support team: https://support.atlassian.com/contact/#/ I see no open defects for this symptom in the public backlog,…

Hi @hamood_rana -- Welcome to the Atlassian Community! That is possible if you store the Slack member id values in Jira also. One such way is to add a user entity property with each person's Slack member id, and then access that property from inside the rule. Please see this article with the steps required to get the id…

I am unclear how that could have worked if the field was always a multiple-select, user field, and now has suddenly stopped working with no rule changes. Let's try the fields syntax to set the field in one step: { "fields": { "Approvers" : [ { "id":"xxxx" } ] } }