Bill Sheboy Expert

Hi @robert_tarver When asking for help with JQL, please consider the following so the community has some context to offer suggestions: * What problem are you trying to solve? * How often do you need to solve this problem? This can influence the tools people may suggest. * What have you tried thus far? If you have a query,…

Hi @Francisco Perla -- Welcome to the Atlassian Community! A question like this seems very specific for the marketplace addon's features, so I suggest looking the product up in the marketplace and see what the documentation indicates is supported. If that is unclear, perhaps contact that vendor's support.…

Hi @Ori Gabai Agreeing with what Rachel suggests, and... There is already a built-in field for that purpose: affectedVersion. I believe that is for the list of versions impacted by a defect (bug). Best regards, Bill

Hi @David Loszewski I am not seeing that symptom for our rules. Is that a custom field for the instance (company-managed projects) or for a specific, team-managed project? Other than checking in with your site admin about any recent custom field changes, consider asking the site admin to submit a support ticket to…

That's curious. If you write the value to the audit log, what value do you see? When I did this, the division worked: {{issue.Original estimate.divide(2)}}

Hi @Lewis Flisher I think you have your signs reversed due to the minus days values, so perhaps try: created <= "-15d" and created >="-20d" and status in ('Waiting for Customer', 'Waiting for Support', 'Escalated') For something like this it can help to draw a quick number/time-line, mark up what you want, and then select…

Thanks for clarifying your scenario. I believe that isn't possible unless you use separate rules in each project or use JQL for each project in a single global scope rule. And there is no generic looping structure in automation rules, so even if you had a project list you cannot make this generic. Of note, global rule…

Hi @Bodavo If you add an ORDER BY statement to your JQL with the Lookup Issues action, that will guarantee that when you use {{lookupIssues.first.key}} it is indeed the latest one. Without the order by clause, there's no guarantee of the return order of the issues. Best regards, Bill

Hi @Ravi Sagar _Sparxsys_ FYI...I do not believe a created variable will always work in this use case: * It will work when a branch returns one-and-only-one issue, as the branch converts to in-line code * But when there are multiple issues returned, each issue is processed separately and asynchronously; so the created…

Hi @Aidan Farnan I saw another post that the Agile Wallboard Gadget is now showing the same "retirement" message. Makes me curious how many other gadgets are being sunset, with the gentle suggestion from our vendor to purchase marketplace addons or upgrade to premium licensing. I couldn't find anything on the public…

The .divide(2) will definitely work, and I suggest you check your site settings for the definition of working day to see if that is the problem with what you are seeing. When you enter values in original estimate, the working day is used; it isn't a raw number...no matter how you enter it. For example, my work-day set up…

Hi @Max Mykhailenko What problem are you trying to solve with this automation? It seems like a list of the issues in each project. And...I do not believe there is a {{project}} smart value, and if you have more than 100 issues in a project, that Lookup Issues could only process the first 100. Best regards, Bill

Hi @Meital Adir It looks like your update JSON looks correct (other than that stray "d" character), and the smart value for original estimate is the error. Please try {{issue.timeoriginalestimate}} for single issues or for issues which have children try {{issue.aggregatetimeoriginalestimate}} One challenge with automation…

Thanks, @Raffaele Litto !! Looks like they have improved the API so the automation rules can use that. Let's see what they update in the defect/suggestion. Please mark your own answer as "accepted" as that will help others find this solution in the future. Thanks, again! __Bill

Hi @Ron Feldman Would you please provide your complete JQL statement? That may reveal more information about what is happening. Thanks! Best regards, Bill

Hi @Daniel Satnic -- Welcome to the Atlassian Community! I do not believe that is possible with out-of-the-box features. And, median age (or another percentile) might be a better measure than total. Or better still, show the histogram of ages. You may want to look at the created/resolved chart, or marketplace addons, to…

Hi @Raffaele Litto According to this defect, automation changelog does not work for components and fixVersion fields yet: * https://codebarrel.atlassian.net/browse/AUT-2013 * https://jira.atlassian.com/browse/JRACLOUD-74953 Best regards, Bill

Hi @Rayno Matthee I do not believe that is possible, probably for the same performance reasons that data for all issues cannot be retrieved for JQL with more than 100 issues returned; batching is required. You may want to try a REST API JQL call to get the issue keys you want and then iteratively call the worklog one. Best…

Hi, Alex. Thanks for that information, and please try to keep your responses in one thread. That will help the community members when they look in the future to see if there are alternative answers to a question. Thanks! Okay, now that we know you are using a team-managed project, you may remove the other values from that…

Hi @Jesse Berkeley Agreeing with Jack's suggestion, and... for more intrusive automation rules, I create a test project (or Jira instance) and exercise them there first. Once validated, it is easy for the site admin to copy them to target project(s) for final setup. Other techniques are: * change your planned trigger for…

Hi @Lee Street Yes, and...to what Jack suggests: * I recommend reading this documentation page for the Jira interpretation of a control chart report. It has a lot of useful info, but it is a bit tricky to get it set up to show what you…

Hi @Alex Artyomov -- Welcome to the Atlassian Community! Here are some follow-up questions which may help the community to offer you suggestions: * Are you using a company-managed or a team-managed project? Company-managed uses {{issue.Story Points}} and team-managed uses {{issue.Story Point estimate}} please note the…

Hi @Julio Cesar -- Welcome to the Atlassian Community! I will assume you want to do this only for the "in progress" issues... You may list those issues with this query, substituting in the name of your project: project = myProject AND statusCategory = "In Progress" AND NOT status CHANGED AFTER -7d If you are using a…

Hi @SHACHAR HAR-SHUV To add to what Jack suggests... Please look at the epic panel on the backlog, select the down-arrow at the right of an epic, and then select mark as done. Best regards, Bill

That is curious... That seems to behave as if issues are being found without "CLONE", and/or issues are being processed multiple times, and/or there is a timing issue. Would you please post an image of your complete rule and of an execution from the audit log? After that, please try to write the modified summary to the…

Hi! To help focus a bit, I am using Cloud, not Server version; so my results may be different from yours... * When called from a sub-task issue type: {{issue.parent}} returns the key and {{issue.parent.summary}} returns the summary * When called from a story or bug, these will not return the epic. To get at those you would…

Hi, Pascal. I do not know if such a feature is planned as I am just a user. Checking the public suggestion backlog I didn't see that idea in there.

Hi @Rafael Francisco Garabato Bonino As I initially noted, I believe you can do this with text functions and regular expression searches. You probably will also need the list functions (to split values) and the Create Variable action for temp variables. Your use case is unique for your needs, and I suggest trying to build…

Thanks for that information. A couple of follow-up questions: * Where is this rule stored: as a global rule or in the project you note? * In the rule details, please show an image which shows the scope field I suspect what is happing is this rule was created at the global scope, even though you just need it for one…

Hi @Dennis_H A lot about using automation rules is experimentation, so I encourage you to try things to learn what does and doesn't work. The documentation will not have all of the answers for every use case, so consider writing a rule, and if you have a problem then post that rule and the audit log for the community to…