Bill Sheboy Expert

Hi @Louise Baker For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Felix van Dijk Yes, and...to John's suggestion: You may want to consider adding a condition to test if the "End Date" minus the 180d is in the past (before the current date). That may prevent mistakes / errors in process. Kind regards, Bill

Hi @Rees, Ian Short answer, please try this: {{varSource.replace(varOne, varTwo)}} Where the variables are defined as this: * action: create variable* name: varSource * smart value: Here is my number one text * action: create variable* name: varOne * smart value: one * action: create variable* name: varTwo * smart…

Thanks for the information, @Yuan Jiang For the change to show / collapse the transition labels, did the team consider having an additional visual indicator when the labels are collapsed? For example, use a different line shape / style, rather than have the same line for transitions with no action / condition. Kind…

Ah, you also need to Log Work after that write to the audit log :^) Please re-add your Log Work action, with the smart value: {{issue.created.diff(now).hours}}h Writing to the audit log helps to diagnose rule problems / see progress, but does not update any issues.

I am glad to learn you have a workaround! Regarding my other suggestions...my apologies in advance for the longer post / explanation :^) First, an explanation of the challenges and then the workaround. In my experience, two limitations with automation, list iterators are scoping and data availability. Only data at the…

Please add the log action to your rule, run the rule to test it, and the post an image of the audit log details. And, please try reversing the values as time logged cannot be negative: {{issue.created.diff(now).hours}}h

Hi @Simon Ma Awesome; I am glad to learn that approach worked for you! Regarding your question, "how can anyone get to this solution", are you asking how may one learn to create such solutions? If so, I suggest a lot of experimentation and learning about rules...or at least that is how I have been trying to do so. That may…

Based on the image you posted, you are using a Jira Cloud, Team-managed Project (TMP) with a Scrum board. Is that correct? I recommend pausing to review the sprint burndown report for both sprints. That will provide a detailed accounting of what Jira detected as the commitment and changes in scope (i.e., stories in sprint…

Again in my opinion, solving this scenario with an automation rule is not helpful for a team, and I question if the "assignment" is missing information about why it is needed. Made up scenarios like this make me wonder: exactly what concept is being taught that the solution would undermine the team's health? Regardless of…

Thanks for clarifying the scenario. Now for some adjustments to your rule... First thing: your rule will try to access data outside of the JPD project, and so it must be either global or multiple-project in scope. Your Jira Site Admin will need to help change the rule scope, so please chat with them about the rule. What is…

Awesome; I am glad to learn that helped!

Hi @Sakthidasan Viswanathan -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer suggestions. Until we know that... JPD projects do not use Versions / Releases. And the specific values for a Fix Version field in a linked "Delivery…

If the start-print dialog shows 0 issues, that has nothing to do with rules or webhooks. Please pause to understand why that sprint contains no issues. Back to the solution I recommended, when that rule starts, it has no issues. It only gets the sprint id value from the webhook called. You described wanting to send a…

In my last post, did you see my note about the allow-rule-trigger option? If an automation rule creates the issue, that event cannot trigger another rule unless the allow-rule-trigger option is enabled.

As noted, those fields are not available yet for Jira Data Center's version of Lookup Issues. Here is the suggestion to add them: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 There are two possible workarounds for this: * when you need the data to send an email or message (like your case)* Remove the lookup issues…

Thanks for that additional information, @GlenellRosburg The Re-fetch Issue action may be added from the list of actions. Here is the documentation on it: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data Just select that line under the trigger issue and the plus-sign + to Add…

Hi @Tanu Bhandari -- Welcome to the Atlassian Community! Do all of the missing people have issues assigned to them on the board? I believe only the avatars for the current user, "unassigned", and people with currently assigned issues appear. Kind regards, Bill

Hi @GlenellRosburg Please also post an image showing the complete audit log, and audit log details for the rule execution, to provide more context for this symptom. How is the new story added to the project? Is another automation rule creating it, a person doing it manually, or some other method? What is the scope of this…

Hi @Anthony Amirfar First, please try adding the units of measure for hours to the end when you log that time: {{issue.created.diff(now).hours}}h If that does not help, please add the Log action (not the Log Work one again) to your rule to write out that expression. Then re-test to observe if it has the value you expected…

First thing: when inside of an iterator such as {{#lookupIssues}}...{{/}} do not add the {{issue. prefix to the fields. The scope is now the lookup and not the "current issue". Please try removing that and re-test: <td style="border: 1px solid #000000" valign="middle" align="center"> {{customfield_30732.value}}</td> <td…

Hi @Helle Friis Pedersen -- Welcome to the Atlassian Community! I am working on an article on searching list fields, such as attachments; until I post that... It seems a "simpler" workaround is possible as the changelog can now return just the added attachment's identifier. And so a REST API function may be called with the…

Hi @Krishma Sood -- Welcome to the Atlassian Community! Although it is possible to do this with automation rules, I encourage not doing so. Instead first consider discussing with the team what is happening, the root causes, and how to improve. What you describe may be a symptom of other possible challenges. For example: *…

Hi @Sofia Marchione -- Welcome to the Atlassian Community! The built-in dashboard gadgets do not support interconnecting them for their filters. I believe there are marketplace addons which can do this. Without seeing the specifics of your dashboard and gadgets used, other options could be: For the current open sprint for…

Hi @Mike Oragwa That report, and other sprint reporting, is based upon when the sprint started and ended. If the user stories were not in the sprint, or not yet sized with story points, those values would not be included in the "commitment" on the report. Similarly, if the sizing changed after the sprint completed, the…

Hi @Aditya Johar -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @ORG_Admin_ENSOC_JIRA -- Welcome to the Atlassian Community! The smart value {{initiator}} may be used with conditions to limit the rule actions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#--initiator-- The rule will still trigger, but if it performs no actions which count for usage it…

Thanks for that additional information, Matthias. For some follow-up questions... What is the type of your field: date picker, date / time picker, something else? Is that a custom field you added, or is it from a marketplace addon / app? Please post an image of your complete automation rule, an image of the clone issue…

Will your dates always be the start / end of months? If so, add one day to the end date before performing the math. {{issue.Budget Coverage Period (Start date).diff(issue.Budget Coverage Period (End date).plusDays(1)).months.abs}}

Let's back up a bit, as I believe we are confusing the different rules for the scenario... Please take a moment to test the JQL used in those conditions and actions with example issues using an issue search to see if they return what you expect. If not, adjust them. For example, the Tasks are indirectly related to the…