Bill Sheboy Expert

Hi @Jose Ortega Sorto -- Welcome to the Atlassian Community! Please see the how-to article posted earlier in this question on how to call the REST API endpoints from a rule using the Send Web Request action. Kind regards, Bill

Hi @Josh Schoenick This is a very old thread, and thus I recommend creating a new question, perhaps adding a link back to this one. That will ensure the maximum number of people see it to offer suggestions. Thanks! When you post your question, please include images of your complete rule, the edit action, and the audit log…

First thing: the call to the REST API should be before the attempt to edit the issue fields. Next, as you can see in the audit log, the issues are in the web response body, with the custom field under the fields attribute. That will return as text, and so must be converted into a date so the max function will work. Please…

Please show images of your current Edit Issue Fields action and of the audit log showing thee rule execution.

The rule you describe using Sprint end date information is slightly different as it needs to find that information to decide when to send the notification. There is no built-in template rule for it... First thing: in my opinion, reminder rules like this are a "smell" of a root cause / problem, as the team's daily scrum…

Hi, @Travis Hill The JSON you show is missing a closing curly-bracket: they need to be paired up to match. And, that is assuming that structure works for the field type. When the field is text, the JSON would be this: { "fields": { "customfield_12971": "{{customval}}" } } When the field is another type, please look here to…

Hi @jankajeriksen (gmail) -- Welcome to the Atlassian Community! First, copying comments during issue cloning is not supported by built-in features. Workarounds including using marketplace addons or automation rules (with some limitations). Next, would you please explain your scenario? The rule you show will attempt to: *…

Hi @John Erickson -- Welcome to the Atlassian Community! One challenge with the original, automation template library is the names / IDs of the rules have evolved over time and the links were not updated accordingly. That specific rule was renamed to be more trigger-oriented: "When a task is near due → send email reminder"…

Hi @Rahul Mittal By default, automation rules have single-project scope. With this, they can create (or clone) issues into other projects, but cannot access them in any other way. What this means for your scenario is it is likely the lookup issues action you use cannot access the issues. That can be fixed by working with…

Hi @Diego Martínez You describe trying to update the Target End date field in an Epic using the maximum value of the child issue Stories. As you are using Jira Data Center, I believe there is only one way to do that to get the value: calling the REST API to access the maximum value for the edit. For Jira Cloud, this is…

Thanks, @Vojtech Kalab I should have asked to see your complete rule as it likely was impacted by the known timing problem with the Issue Created trigger where it fires before all data is available to the rule. Generally, it is a good idea to always add Re-fetch Issue immediately after that trigger.

Hi @Rob Marshall You describe moving issues from a Company-managed to a Team-managed project. The Sprints are associated to the project, and so anything you try to re-create / re-assign the Sprint field values to the new project will not preserve reporting, etc. in the new project as the Sprints did not happen there. For…

Hi @Asad This question is for Jira Cloud, and that does not have customer-accessible database indexing features. What is the source of the information for your suggestion? Kind regards, Bill

Thanks for testing, and it appears the defect I noted earlier also applies to the date / time functions. You could confirm that by contacting the Atlassian Support team for their input.

I recommend inverting this to update the parent when children transition: * When the first child issue transitions to an "In Progress" status category, update the parent. * And the likely follow-up rule would be when the last child issue transitions to a "Done" status category, update the parent. This approach will be…

Hi @Armin Muminovic -- Welcome to the Atlassian Community! There seems to be a related defect for this symptom where the background update (caused by two people / processes updating the issue) make it lose focus...and so triggering shortcuts: https://jira.atlassian.com/browse/JSWCLOUD-26549 Have you checked if multiple…

Hi @Vojtech Kalab I recommend checking... * has something changed in the way the REST API endpoint is called, and * check with Xray support / documentation to learn if something changed with the REST API endpoint you are calling. Kind regards, Bill

Hi @Lynette A. Nettles -- Welcome to the Atlassian Community! For a JQL related question, please show the JQL expression you are using and explain what does not work as expected. That will provide context for the community to offer suggestions. Kind regards, Bill

Thanks, and I am fairly certain that syntax will not work with automation rules with JSON. Instead you could use one of these: * created variables and if / else conditions to set them, then use the variables to set the field value with JSON * a single, long conditional expression with the or() and and() clauses to provide…

Hi @Proenge -- Welcome to the Atlassian Community! The answer depends upon your type of project: team-managed or company-managed: For team-managed projects, there is no configuration setting and the issues will drop from the view in 2 weeks. Here is a suggestion to make that…

Hi @Anastasia Sobol -- Welcome to the Atlassian Community! I suspect that information cannot be found with smart values as it is outside of Jira for the addon / app. You may want to check the Xray documentation to learn if there is a REST API endpoint that could be called with the Send Web Request action in the rule to…

You described the "what" you are trying to do, and not "why do this". Such as, "why is proof needed a reminder email was sent?" In my experience, sending scheduled reminder emails is a "smell" there is a root cause, process problem. Perhaps meet with the team to use a 5-whys or other RCA method to learn that root cause and…

Oops, you are correct: I had the JQL for the lookup issues action reversed. It should be: key = {{triggerIssue.parent.key}} I updated my earlier post to match.

Hi @Kerry Penhallurick -- Welcome to the Atlassian Community! That is not possible with the built-in features of JQL. Your workaround options depend upon how frequently you need to do queries like this and willingness to invest money / time: * need this one time* export the issues' fields to a spreadsheet and perform the…

Awesome, and well done! Shouldn't that comma in the expression be a period (any character token)? {{varReporterGroups.split(", ").match("(bot-squad-.++)")}}

Hi @Tomislav Tobijas Some scenarios / anti-patterns where I recall community posts where the limits could be reached include: * "The never ending story"* Teams use an Epic as a "bucket" for things like "Waiting for review", "Prod Support", etc. and so the comments, etc. churn forever-ish * Teams use a single issue to log…

Hi @omerro Adding to the suggestions from @Valerie Knapp here are some other things to check: Does the board filter not specifically include your Wix-Blocks project: https://jira.atlassian.com/browse/JSWCLOUD-27246 Are there so many sprints that the matching one is not visible when the option is…

Greetings, community! Regarding this merging of JWM into Jira, please see the question below where someone asked Atlassian Support about the impact on automation usage limits. Spoiler: it appears usage maximums are reduced (again), eliminating the counts JWM provided.…

@Nicolás Guzmán -- It seems the Atlassian Support response indicates what I hypothesized: there will be one total and it will not increase; instead it will be the maximum of whichever value existed before, by license level. That means the new (total) limit for usage of rules in Jira and JWM will likely be: * Free: 100 *…

Hi @Francesc Juventeny As you have the email address, the rule could call the REST API endpoint to search for a matching customer and then test the response for any found: https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-servicedesk/#api-rest-servicedeskapi-servicedesk-servicedeskid-customer-get For…