Bill Sheboy Expert

Hi @Andy Tran Solving the scenario you describe is relatively easy by changing the rule trigger and including some conditions. However... What problem are you trying to solve? That is, "why do this?" Storing the same information in multiple fields seems likely to cause problems and confusion when people look at the issues.…

Hi @Tyden Ruud Adding to Trudy's suggestions... With the Sprint Created trigger, the {{sprint}} smart value is provided: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--sprint-- And so the rule could directly enter the ID when the story is created as {{sprint.id}} Many fields in the…

Thanks for that information, Michael. I have not tried to add those with a rule, and I believe they are macros which create the list from the selection criteria (e.g., URL, search results, etc.). Many of the macros cannot be directly added by a rule's edit action. One way to check is to view the configuration for the macro…

Hi @Samuel Prathipaty I do not know as I do not use that app / plugin. Perhaps check with the vendor's documentation to learn if it will help. Kind regards, Bill

Please try selecting the "Use cron expression" link in the trigger and view the docs for the guided information on building a monthly expression.

Hi @Michael Dawson -- Welcome to the Atlassian Community! What do you mean by the "List view"? * If you mean the relatively new feature of showing a list of issues within a field, such as within the Description, I not not believe that can be done from an automation rule as the markup is limited. You could try experimenting…

When you want to loop through the issues, use a Branch on JQL instead of the Lookup Issues action.

Hi @Raina Anand What have you tried thus far using the Scheduled Trigger? Please post an image of your rule trigger and the audit log details, explaining how it does not work as expected. In both the automation documentation and the editor's trigger description, it links to information on how to make a CRON expression,…

Hi @David Loszewski Your created variable {{atVAR}} apparently contains: CDI-94, CUS-39 And that is used in a dynamic JQL expression for the Lookup Issues action: issue IN linkedIssues({{atVAR}}, "Child of") However, the linkedIssues function only takes one issue as a parameter, optionally followed by a list of link…

For the diff() you are using, please try reversing that expression: {{#lookupIssues}} * {{key}}: {{created.diff(now).days}} {{/}} I recall a different defect related to using {{now}} first in diff() calls.

Hi @Colin_Turner -- Welcome to the Atlassian Community! This symptom is a known defect where when the diff() is used in a lookup issues iterator the first issue's data is always used: https://jira.atlassian.com/browse/AUTO-334 Kind regards, Bill

As a reminder, the Atlassian Community is a place for people to learn and collaborate, not to provide turnkey solutions for specific scenarios. I recommend trying the suggestions offered, including reviewing the docs, maybe writing intermediate results to the audit log, etc., to learn what helps. For more details to what…

Hi @Katya -- Welcome to the Atlassian Community! The Issue Updated trigger will not fire for a change to an issue's entity properties, and there is no built-in automation rule trigger for such properties. As a workaround, a webhook may be used: * Create an automation rule with an Incoming Webhook Trigger to perform your…

Hi @Marcin Kupisz Yes, and...to the suggestions from @Stefan Salzl Rather than using the Advanced Branch, you may extract the mentioned users' account ID values and add them in one step, using inline iteration and dynamic JSON. This will reduce the risk of errors / racetrack problems due to the parallel processing of such…

Hi @Annu Satpute What you show will not work with Jira Cloud's, built-in JQL features: a JQL statement cannot compare fields in the issue to one another. It is not a SQL. There might be marketplace apps to support such comparisons, and they are likely not in the syntax you show. What is the source of your information for…

Hi @Mattia Gibilaro -- Welcome to the Atlassian Community! That is not possible with the build-in features of JQL. As workarounds you could: * investigate marketplace addons which add to JQL, or * you could use the CHANGED operator and hardcode the Start Date in the JQL Please see this documentation page to learn more…

Hi @Paul Reeves -- Welcome to the Atlassian Community! What Jira license level are you using? There is an early-release-only JPD for Premium license customers that has Idea…

Looks like the behavior is different for Data Center and so you may rely upon the technique you found.

Hi @Renata_Getint What is the source of the content you posted? If it is from a bot / AI-tool, please see the community guidelines regarding the disclosure of such content in your post's wording: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Renata_Getint What is the source of the content you posted? If it is from a bot / AI-tool, please see the community guidelines regarding the disclosure of such content in your post's wording: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

I am using Jira Cloud, and wonder if you try this what you will observe: * identify an issue which has never had a Fix Versions value * enter the value for "2025 October", and save your changes by leaving the field * enter the value for "2025 August", and save your changes by leaving the field What is the order of the…

Greetings, community managers! Please move this vendor / partner article from the Jira product area to the App Central group: https://community.atlassian.com/t5/App-Central/gh-p/app-central Thank you, and kind regards, Bill

Hi @Jeffrey_Denton Short answer: I recommend using the longer math format for this calculation, such as with this: {{#=}}ROUND( {{lookupIssues.timetracking.timeSpentSeconds.sum}} / ( {{lookupIssues.timetracking.timeSpentSeconds.sum}} + {{lookupIssues.timetracking.remainingEstimateSeconds.sum}} ) * 100, 0){{/}} As a…

Hi @Jeffrey_Denton For this scenario, you may not want to use the Lookup Issues action to detect the child issues' status to transition the parent. Instead, please try the Related Issues Condition once inside the branch to parent. There is a template rule for this scenario, which is available under the templates in the…

Yes, that is likely possible in two ways. I recommend the first approach using Lookup Issues as it is easier to test, although the rule is slightly slower rule to process. * Using Lookup Issues* Before the branch, use the Lookup Issues action with JQL to find the correct issue based on the linking to the trigger issue *…

To confirm, is the rule now working as you expected?

That is curious as both should work, although producing different results... I recommend performing the division after the sum: {{lookupIssues.timetracking.originalEstimateSeconds.sum.divide(3600)}} The reason is the smart value originalEstimateSeconds is an integer, and inline math operations preserve the typing.…

Please try wrapping that in a math expression for the division to convert from seconds to hours: {{#=}}{{lookupIssues.timetracking.originalEstimateSeconds.sum|0}} / 3600{{/}}

Hi @Francisco Navarro For an automation question, please also post an image of the audit log details showing the rule execution. That will provide context to see which steps in the rule processed. Also, what is the scope of your rule: single-project, multiple-project, or global? You describe the issues are in different…

Thanks, Trudy. The part I am not quite following: if the Slack ID already existed in Jira would the RBR be necessary? I was helping with another question to add Slack ID values as entity properties to Jira users to ease back-and-forth messaging. There is an old article on this for bulk-loading them, and my approach is a…