Bill Sheboy Expert

Greetings! As an update to this solution approach, to handle the possibility of issues in multiple sprints, and which overlap for different stories. The result produces a distinct list of sprints.…

Well done! I recommend periodically checking for feature changes to automation rules. If / when the advanced branching on smart values is added for Jira Data Center, all of your cases can be collapsed into a single loop. Here is the backlog suggestion if you want to watch / vote for it to see…

Did you expect to get that many issues back? If you manually test that JQL outside of the rule, with an example value for the field, does it only return the issues you expected? Finally, do you mean that custom field is single select or multiple select?

Yes, using either a related issues condition with JQL to check before creating the issue in the branch...or, using a Lookup Issues with JQL and then checking no issues were returned. I recommend trying the related issues condition first; you will need one before each issue create action.

Wow; I am glad to learn you found something that works! Please consider...any approach that requires a lot of rule changes for updates to your user-to-country list could lead to errors. Be on the lookout for other approaches to solve this in the future.

Thanks for checking those fields. I just reviewed the open suggestions and found the Lookup Issues action for Jira Data Center does not yet support those fields: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 The same thing happened when Lookup Issues was added for Jira Cloud, and it was about a year later when all…

Hi @nicholas kurtz -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud and not Data Center version, and so cannot verify what I am suggesting. My ideas are based on what I know about automation rules. With that out of the way... There are several smart values for time tracking, some of which are…

Hi @Whitni Smith -- Welcome to the Atlassian Community! Adding to John's answer... I also recommend working with your Jira site admin to submit a ticket to Atlassian Support: https://support.atlassian.com/contact/#/ This symptom has been happening for at least a couple of weeks, according to my observation of community…

Hi @Pete Ross Short answer: no. The Jira burndown chart shows all of the issues in the sprint for the board's filter...which is not configurable for team-managed projects. If you need a more configurable burndown / burndown-like chart, you could investigate marketplace addons or use a company-managed project and adjust the…

Hi @Karin Biedermann and @John Funk John, did you mean to use AFTER startOfDay(-5M) rather than > startOfDay(-5m) in that query to use months? Karin, here is some free training and documentation from Atlassian to learn how to make such queries in the future: *…

Hi @Amy Chang Agreeing with John's suggestion, and...some questions to clarify the use case: Do you want the Initiatives to also update for those scenarios, based on changes to their child Epics? For either of your rules, have you enabled the "Allow Rule Trigger" setting in the rule details at the top? Enabling this option…

Hi @Vincent Dufour Adding to John's answer: Are these team-managed, company-managed, or one of each type projects? You may find that information at the bottom-left side of the page's expanding area. While company-managed projects share issue types, team-managed projects each have their own configuration. And so using the…

Hi @Søren Hansen For Jira Cloud automation rules, please see this documentation for the match() function and its use of regular expressions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- The match() function returns a list of matches. To access a specific one, please use the…

Hi @Sachin_Argade -- Welcome to the Atlassian Community! Adding to John's answer... Here is some free training and documentation from Atlassian to learn how to make such queries in the future: * https://university.atlassian.com/student/activity/1225443-intro-to-jql-in-jira-software-course-description *…

Hi @Sajeeka mayomi That appears to be a dashboard gadget from a marketplace app / addon. Please check the vendor's documentation / support to learn how to do what you ask. Your Jira site admin can help identify the vendor and product to check. Kind regards, Bill

Hi @Sia (Nastassia) Sharasheuskaya For some context, would you please post images of: * Your complete automation rule in one image. That may require a scrolling browser capture, with a browser extension or screen capture tool. * Your entire audit log details for the rule execution you describe, again in one image * Your…

Oops...my typo! I corrected my posted answer based on what you found. Thanks!

Please note in you rule you are using two different conditions: * if Component / s equals (in any order)... * if Component / s contains any of... I believe you want to use the contains condition for all of your tests; otherwise it will only look for an exact match to the values noted.

Hi @Debs Olivares -- Welcome to the Atlassian Community! Would you please show the audit log details with the rule execution? Looking at that, and an example issue with this symptom may help. What is the type of that custom field: text, single select, multiple select, etc.? Also...if you add that condition directly to your…

Hi @Neville If the values are the same between the input and the multiple-select custom field, you may do this with list iteration and advanced edit with JSON. The challenge for a scenario like this is in the details: your webhook data must be correctly parsed to create the JSON message. Based on what you described that…

Before doing this, my question would be: what problem is this solving? Some workarounds I can think of are: * Don't do it. If the data is being passed to another system, it is likely systems / code outside of automation rules can do this more easily so let them handle the conversion. * If you know the maximum possible…

I was not able to find support for that in automation rules, such as with the format() function.

Hi @jprieto Short answer: no, however... What actions does your rule do when one of four fields are changed? If this is a one-time action, the rule could be triggered on a change to any of the four fields, and then immediately after the trigger use a condition to check if the action happened yet. If not, proceed with…

Kristine, I am glad you got something that worked, and... As there have been multiple reports in the community of this symptom for the last couple of weeks (i.e., 400 error with the Clone Issue action), I hypothesize something has changed in the automation engine, the REST API, etc. that is causing this. Hopefully the…

You found the correct field, watchers and its attribute active, and to do what you ask adjustments are needed because looking at watchers is a separate REST API call out of the rule to capture the value of active for filtering. * trigger: scheduled * action: create variable* name: varWatchers * smart…

Certainly! A basic example would be this: * When a field / data is needed in a regular expression, first create a variable* name: varRegEx * smart value: (value1|value2) * Then when searching a field / list, the varRegEx may be used in a match* {{issue.someField.match(varRegEx)}} There are some extra steps if the search…

Hi @Kalyan Sattaluri Did you confirm that expression works for a date field type for Server / Data Center? I know the null handling tests can vary by field type and whether or not the field was previously cleared...at least for Jira Cloud automation that is the case. Thanks! Kind regards, Bill

FYI, here is the suggestion to add those other fields to Lookup Issues for the Data Center version of automation: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 If it is of any consolation, when Lookup Issues was added for Jira Cloud, it also only had about a dozen fields. About a year later, all of the remaining…

Thanks for that information, and...I'll admit I spent a long time trying to get your scenario to work yesterday before I deleted my long-ish post to ask that question instead :^) I also decided a delimited variable would be better than the table for the country-to-user mapping and the branch should iterate at the user…

Hi @Tracy Boyd As the sunset of the "parent link" field proceeds, I recommend using the "parent" field. Please look here for some information, but not the specific timelines as that has not be announced fully. https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ Kind…