Bill Sheboy Expert

Hi @Apoorva Pahuja When your use case requires a change made by rule #1 to trigger another rule (e.g. rule #2), look in the details section of rule #2 and enable "Allow Rule Trigger". This is disabled by default to prevent a looping/runaway situation in rule execution. After enabling this option, keep a close watch on the…

Hi @Athas Mark Short answer: no, that is not possible with out-of-the-box Jira. Longer answer: The drag-and-drop ordering of a backlog works when the filter contains ORDER BY Rank ASC. If you changed the order expression the drag-and-drop no longer functions. A work-around for what you describe is to use quick filters by…

Hi @Bård Karstensen I notice there is a typo in your JSON expression: {{triggerissue.customfield.10091.accountId}} should be {{triggerissue.customfield_10091.accountId}} Kind regards, Bill

Hi @Maria Chrysanthopoulou -- Welcome to the Atlassian Community! You are probably using some smart value expression to create the new version, such as: * Release for {{sprint.name}} Whatever value you are using to create the version, try first setting it to a created variable and then use that value to set the fixVersion.…

Hi @Christine Byrer Would you please post an image of your current rule to provide some context? Thanks! Are you trying to copy/match the epics to the children, or might the children have more labels than are present in the parent epic and you want that preserved? Kind regards, Bill

Hi @Matt Holdgate I do not believe you can chain those two functions, as MembersOf() tests if a field is in a group and updatedBy() only accepts users, not groups. You may want to check if you have any marketplace JQL addons as one of them may support such a query. Kind regards, Bill

Hi @Razmik Mikayelyan You could use list functions with your custom field to iterate and mention them all. For example: Mentioning approvers for action: {{#issue.Approvers}} [~accountid:{{accountId}}] {{^last}}, {{/}}{{/}} This iterates over the values in the custom field, adding a mention for each person selected. Kind…

Thanks! Yup, that is what I expected was causing this. In general, you only need the branch For Current Issue if you are using a single condition test *and* want processing to continue after some processing. For your rule to do what John suggested and following your example, please try this: * trigger: issue created *…

Matt, would you please show an image of your complete rule? I believe the image you posted for condition test options only appears when inside of a branch, and so if/else is not permitted at that nesting depth. Outside of a branch you should see all of the options for conditions. Thanks!

Hi @Matt Crist Yes, and...to what John suggests: I wonder if your email message is identical for the different sites, with only the List A, B, etc. different for the recipients. If so, you could use the IF/ELSE described by John to set a created variable to the recipients, and then use one action to send the email. To go…

Thanks for your rule image and additional information. I should have been more clear that I was suggesting to use a condition in the rule. For example: * trigger: issue created * action: Re-fetch (to prevent the known timing problem which could occur) * advanced compare condition: * first value: {{issue.components.size|0}}…

Thanks for that information. To respond to your specific notes: I try to use a #issue.customField_16304 to get the list of Epic (custom field 16304 give me the name of epic). But it's not working For the branch you are using the bulk-handling feature in order to send one email and to get the smart value {{issues}} to work.…

Thanks for that information. I believe your rule should then work as you expect. The only part to decide is using the custom field in your webhook to schedule the Jenkins job. Please see this information for formatting date/time fields: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Thanks for that information. That means the issue links only contain the keys, as I suggested. To sum up the story points for linked issues you may to use another method, such as Lookup Issues with JQL on the list of issue link keys: key IN ( {{#issue.issuelinks}} {{key}} {{^last}} , {{/}} {{/}} ) With that for the…

I am glad you solved it, Diana. Out of curiosity, did you see an error trying that in your automation rule, or in some other way? And, what error did you see? When I tried that in a rule similar to what you note it worked without error.

Hi @Diana Leon -- Welcome to the Atlassian Community! You could check the number of components with the following in your rule: {{issue.components.size|0}} You could use that in your issue created rule, or in another rule checking for changes to components. With JQL, I believe with out-of-the box features you may only…

Regarding move, I recall seeing some open issues on moves correctly providing the "from" for automation. How about this: split the problem so you have one rule which roles up subtasks to the story, and a second one for stories to epics? Having two rules reduces the complexity, simplifies the testing, and will generally be…

Hi @Alexandre ANTOINE I am using Jira Cloud, not Server/Data Center, so it would help me to see an image of your complete rule to offer suggestions. Would you please post that? Thanks! Until then, I suspect you are using something like this as your rule: * trigger: sprint completed * branch: issues in the sprint (or with…

Sorry, but I am at the limits of my entity property knowledge on this one. Something that helped me using properties was to call the REST API from a browser, adding the properties parameter, to see if the values were being set with a different key/value or at another scope level:…

Thank you for that information. Was one of the issues you expected to see in the branch loop the trigger issue? Is so, automation rules add exclusion JQL to remove the trigger issue from branches. This prevents a possible collision, looping, or duplicated processing conditions. The work-around would be to add the comment…

From what you describe as your steps... * An issue is created manually * The custom field "Scheduled Date and Time" is set on the issue manually * A comment is added to the issue manually * An automation rule detects the adding of the comment, checks some conditions, and then schedules a Jenkins job Is that correct? If so,…

I am glad to learn that is working. Please consider marking this question as answered; that will help others with a similar need in the future find solutions faster. Thanks!

First, I was suggesting to try logging the values without summation. That will confirm if the values are even present. If so, then investigate why they are not summing. If not, you will need another way to access them, such as a branch on JQL. Next, the connection between epics and child issues depends upon your project…

Thanks, Anne. Just to follow-up, when you try the delete issue, does it detect that as changing the links in the trigger for any linked issues?

Awesome! I am glad to learn that helped you.

Hi @Craig Cinder -- Welcome to the Atlassian Community! Did you note that we were constructing {{sprintStates}} as a created variable from the list of sprints, and that it is not built-in? Please look earlier in the thread if you missed that. Otherwise, how similar/different is your use case to what Jason was trying to do?…

Hi @Oliver Monaco -- Welcome to the Atlassian Community! This is curious...it appears you double-posted this question, and my answer in the first one was deleted when the duplicate was deleted! Oh well... I have seen the set entity property action in automation rules does not work when there are non-alphanumeric characters…

Thanks @Darryl Lee and... * Perhaps the author and team do not want to start a never-ending thread of people commenting on this very high-impact issue and decision. (Pause to consider how many vendor apps will be impacted.) Perhaps a better platform for this announcement would have been the weekly post/email on changes. *…

Please try instead adding: AND labels IN ("iOS", "Android", "Back")

Hi, @Darryl Lee Yes. I made a test rule which can find labels matching a pattern that way. The challenge is then updating the sub-tasks. What I did not try: using a regular expression instead to identify the labels (using conditional list processing), store that, and then iterate over the sub-tasks in a branch. Kind…