Bill Sheboy Expert

Hi @[deleted] 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 @Davyd Derkach -- Welcome to the Atlassian Community! First thing, I am not currently using the dev ops triggers and so cannot experiment to figure out this symptom empirically. As for additional documentation, I have not found any for the specifics of these triggers beyond this…

Hi @Glenn Ruysschaert Are your rules triggered for Sprint Started and Sprint Completed using global-scope? If so, there are known defects / limitations for those: https://jira.atlassian.com/browse/AUTO-1047 https://jira.atlassian.com/browse/JRACLOUD-80707 etc. A workaround I found for these was to use a global, incoming…

Thanks for that information, Jeremy. Did the support team indicate if this was a behavior of Jira Data Center automation rules or something else? And what did they mean by "new syntax Automation"?

Hi @Matthew Challenger This is possible, and... It would likely take me as longer to implement and fully test this than for you to do so...primarily because you have access to the source sending the message, and so can foresee any challenges and edge cases. Some recommendations to get this started: * pair up with a…

Would you please post your current, updated rule in a single image? Posting in a single image will confirm the step order / context. If the rule is too large for one browser page, you could use a scrolling page browser addon or app to capture the image.

Could the URLs contain mixed case? If so, perhaps force the comments to lower case before comparison. Or, perhaps try using the match() function with your regular expression in the first value to evaluate all comments, and then test if any results are found. {{issue.comments.body.split("…

As you have selected date and time values which span 11 weekdays, the burndown chart shows 11 weekdays. When selecting sprints which span 10 weekdays (or using 2 weeks), the reports will show 10 weekdays. I am unclear how else to explain this, so perhaps another community member will be able to help.

Well done, and... I believe you could instead nest the conditions within the varRemoveLabels block and test for the presence of varAddLabels just to add the comma. That would reduce duplication and the chance of any typos / errors. Or, perhaps the definition you used for varAddLabels is different from what I originally…

Paulo, to confirm the situation: is there a branch in your rule or do you mean the if / else block? * If it is a branch, I would expect that behavior for branches which could be on more than one thing * If it is a single issue branch (e.g., Current Issue) nested within an if / else block, there is an open defect for the…

Thanks for clarifying, and I believe you would need two rules: one triggered on a parent change (which would find children of that parent) and one triggered on a child (which would find siblings through the parent).

Thanks for that additional information. As this sounds like a one-off for reporting, perhaps export a few sprints of data to a spreadsheet and create a simple pivot table. Once the team decides on a next, starting point for forecasting, the team velocity chart could be used going forward...along with discussions at the…

Hi @Asifa Azad (CW) -- Welcome to the Atlassian Community! Rather than increment a counter, I recommend recalculating the count using the Lookup Issues action instead. That will prevent errors and help when handling the edge cases: deleted issue, issue type changes, etc. Next to your additional question for updating…

Hi @Cory Beaudoin This question has been asked a few times before in the community, and if you search you may find the details of the discussions / limitations / solutions attempted. Essentially, if your rule has no branches to create issues, the key of each created issue could be saved with Create Variable, and then those…

Hi @Heidi Vanderholm The built-in Jira reporting for Scrum boards shows measures for the entire Scrum team's sprints as that manner of working is based on collaborative, and not individual, delivery of value. What problem are you trying to solve by measuring for individuals? That is, "why do this?" Knowing that may help…

Hi @Krzysztof Kołodziejczyk -- Welcome to the Atlassian Community! When a field is not listed in the dropdown list for the automation Issue Edit Fields action, you might be able to use advanced edit with JSON to set the value: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ To confirm…

Hi @Matías Völgyi It is not possible to return more than 50 users at a time for that endpoint. I believe you use the cursor parameter with the returned URL from each call. Please look here to learn more about the technique:…

Hi @Alexander Pappert First thing, I am not using Confluence automation rules currently, and so my suggestions are based on what I recall and find in the documentation. With that out of the way... I wonder, could you use a branch on CQL, checking if the parent (or ancestor) is the trigger page?…

Hi @Shushan Kocharyan First, I recommend checking if the time tracking and tag fields are in the data loaded for the subtasks smart value. You may do that by writing these to the audit log: time: {{issue.subtasks.timetracking.originalEstimateSeconds}} tags: {{issue.subtasks.tag}} If the values are present, that will…

You could replace the advanced branch with a branch on JQL with the same JQL I provided for the Lookup Issues action. That will enable iterating over the issues.

Greetings, Project-scope rules may create or clone issues in other projects, but cannot access them otherwise. Rules which access (or update) issues in multiple projects must have global or multiple-project scope. Such rules are defined in the global automation area, not in the project settings. Your Jira site admin will…

Hi @Nenad Neshov I have found only limited documentation on the structure of rule automation JSON, and this is the guidance Atlassian provides for such migrations: * https://community.atlassian.com/t5/Automation-articles/Troubleshooting-Server-to-Cloud-rule-migrations/ba-p/1864435 *…

Hi @Davyd Derkach -- Welcome to the Atlassian Community! The rule's trigger is using the option "Issues provided in the webhook HTTP POST body", and so the steps loop over each issue provided. You could change your rule to instead use the option "No issues from the webhook" and pass only the issue keys in the custom data.…

Well done! Regarding your comment about generalizing this solution (such as for a global-scope automation rule), the automation Create Version action would not help because it needs some context to select the target project: either rule scope or the issue data. A possible workaround would be to use Lookup Issues with JQL…

First thing, please post an image showing what you describe as the "Sprint plan shows 11 days excluding week ends". Thanks! Next, I believe the duration selection of "2 weeks" counts from the start with date / time, and so it runs through to the same time for what appears to be the 11th business day: but it is effectively…

Hi @Simon Ma I do not recall the different tests I tried when I first suggested this solution, and... With a quick test on my original definition for varRemoveLabels, exists() did not work but isNotEmpty() did work. This seems to indicate the iterator which generated the variable is now creating an empty string and not…

You may change the diff() units of measure from days to businessDays: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference--- That will be Monday - Friday, and does not use any site or project settings regarding non-working days or saved holidays.

There are two approaches to to manage the service limit, counting impact when cascading changes through multiple issue levels in the hierarchy: Using multiple rules, where there are separate rules for each hierarchy pair and use conditions to manage that: * rule 1: epic to task changes * rule 2: task to subtask changes;…

Hi @Jamie Zeidler -- Welcome to the Atlassian Community! Just to confirm...was that gadget removed from the ones provided with Jira Service Management (JSM) or did your team stop using JSM...and so the gadget is now removed? Kind regards, Bill

I recommend comparing the cloned issue and its source issue to find what is different between them; that may indicate which field is preventing the filter from picking up the issue.