Bill Sheboy Expert

Hi @Mark Darby The parameter passed to JIRA.JQL() must be enclosed in quotation marks, and when you want a quotation mark in the expression, you double it (such as with "") When I tried this, I created the expression first in a spreadsheet cell, and then referenced that cell in another. That showed me what would be passed…

To identify the correct smart value (and confirm rules support it), please use the how-to article I provided. Essentially what you do is: * identify an example issue with your field * call the REST API from a browser * search for your field on the page* if you find it, you can confirm the smart value (or custom field id) *…

Hi @Achmad Rifki What do you mean by "grouping"? Are you expecting one message or did you want multiple messages? If you want one message...are you using Jira Cloud or Jira Server/Data Center? * Jira Cloud:* You could use the Lookup Issues action to gather the results as a set, and output a single Slack message. To do…

Thanks for that information, Dwight. It appears something has changed as I thought the scheduled trigger was already limited to 100 issues at a time...and that throttling only happened when either the rule ran too frequently or it referenced to many related issues, per each triggered issue. John's approach sounds like a…

Hi @Dominic Mercorelli Please try using the Lookup Issues action with JQL to access your issues, and the max function on your field: {{lookupIssues.myCustomField.max}} To possible limits of this technique are Lookup Issues can only access up to 100 issues, and you note using a short text field (rather than a numeric…

Hi @Lukas Maas When a field is not yet supported with the built-in list for Issue Fields Condition, please try the Advanced Compare Condition and use the smart value for the field To confirm you have the correct smart value for your field (and that it is supported by rules) please use this how-to…

Hi @Amnon Even Zohar What do you mean by "submitted" and "wasn't addressed after 7 days"? Do you mean was created more than 7 days ago and not completed to Done? If so, you could try a simple JQL filter: project = myJPDProjectName AND created <= -7d AND statusCategory != Done Please confirm this works as you expect, as…

Hi @Dwight Holman Yes, and...to John's answer: How frequently are you running that scheduled trigger rule? I ask because that trigger (with JQL) is limited to 100 issues at a time (subject to what else happens in your rule with related issues). If you watch your processing time you may be able to tune the schedule to…

Hi @[deleted] -- Welcome to the Atlassian Community! When a user is mentioned in a comment, that results in the following in the field: [~accountid:thePersonsAccountId] So to get the name from that, I recommend you add a user custom field instead of a text one and... * use a match() function with a regular expression to…

Hi @Rana Paul -- Welcome to the Atlassian Community! If you are using the built-in JQL, that is not possible. JQL helps with issue searching, and if a user has no issues assigned there are no results, and so nothing to report. Using a marketplace addon for JQL or reporting gadgets (or an automation rule), it would be…

Hi @Tom Johnson First thing, is Stack Rank a custom field for your issues, or do you mean the built-in Rank field? Next, have you tried triggering your rule on Issue Transitioned, selecting the desired TO status values? Kind regards, Bill

Hi @Alicia Pena First thing, I am using Jira Cloud, not Server/Data Center version, and so I am suggesting an answer based on what I know about automation rules in general. Onward... One challenge with this scenario is that the links and status are independent: there is no information about one to the other. You might…

Please take a look at the documentation I noted; it fully describes how to call the REST API from a rule. I also provided the REST API method you can call to update the custom field options. Your scenario is uncommon and so you will need to build the rule yourself, and test it to confirm it works as you expect. Automation…

Thanks for clarifying, Jane. As the ABC-123 issue is unrelated to the others, it makes this a bit more challenging to solve. The easiest way to do this is using the Lookup Issues action, with JQL to get at your ABC-123 issue. Please add that action before you create any child stories. And then reference the lookup in the…

Hi @Nancy Tcheou You note Epics and their child Tasks, however your rule is showing summing on sub-tasks. When you want to sum the values for the child tasks, please try using the Lookup Issues action instead, perhaps like this: * trigger: issue created * action: re-fetch issue * condition: issue type is Task * condition:…

Hi @Jane Ellis Would you please provide a bit more context: is ABC-123 the trigger issue (epic), or something else? Kind regards, Bill

The scenario, as posted more than a year ago, is in the original question. It is a pattern to use iterator data within functions when the iterator has no structure. There are other work-arounds for this (e.g., repeated if/else with created variables).

Hi @Slava Gefen Thanks for your suggestions. As I noted to you in my other post for the open backlog/suggestion item on created variables...that does not help in this scenario as the advanced branches are executed asynchronously and non-deterministically. The scoping issues would prevent usage of the accumulator result.…

Hi @Sari Kachorovsky If you know the date/time the update was made, you may review the automation audit log to learn which rule made the change. You may access the log either from the issue view (actions > audit log) or from the manage automation rules view. If you believe this may have been a global scope rule, you would…

Hi @Sherif Safwat -- Welcome to the Atlassian Community! You could either create a saved JQL filter and subscribe people to it, or you could create a scheduled-trigger automation rule (using the same JQL). To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Eden Eliyahu Please review the article announcing the feature release; it describes the usage of the lookup tables: https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333 The short answer is: add key/value pairs for what you want, and then reference them with the…

Hi @Juan José De Arana -- Welcome to the Atlassian Community! First thing, I am just another customer trying to help, and I am not associated to Atlassian or any marketplace vendor. Onward... You are correct: there is no built-in, single field for the "time in status" of an issue. My understanding is this information is…

Hi @Anshul Mittal -- Welcome to the Atlassian Community! First thing, you might also want to look in the developer community for questions like this one: https://community.developer.atlassian.com/ Back to your question...and I have not tried this to verify... That second parameter to setFieldValue() can be a…

Hi @Michael -- Welcome to the Automation Community! First thing: when posting questions about automation rules, please post images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. (As a tip for longer rules, try using a browser…

Hi mike.bruderer@tg.ch -- Welcome to the Atlassian Community! Jira's JQL is not a SQL, and unfortunately cannot compare different issue fields in a query. Some possible work-arounds may be guided by how frequently you need to perform such queries and willingness to purchase addons from the marketplace: * need this…

Hi @Mrudul Raval -- Welcome to the Atlassian Community! The automation rule Send Email action can send to any recipient, not just Jira users. If you have the person's email address in an issue field, try using that in the email action. Kind regards, Bill

I do not believe there is a trigger for forms/form save yet. I was thinking your workflow was altering an issue field in a way that could be detected...and so trigger a rule. I seem to remember seeing a posting about that as a work-around.

Hi @Sanjivani Wayal Because those are three different issue fields, and not part of a structured field like a list, you could try using a series (or nested) conditional expression, testing against your MAX() function call, to get your desired results.…

The key with that one is does the automation rule trigger when you want? If it does, you can put a token value (e.g., REPLACE_WITH_NOW) in the default and then let the rule trigger and replace the token with {{now}}

Hi @Priya Have you tried using a rule with a scheduled trigger and JQL? You can first create your JQL with advanced issue search to test it, and then add it to the rule. Kind regards, Bill