Bill Sheboy Expert

No, the Lookup Table is not needed. It may help because longer math expressions (particularly when duplicated between different rules) can be difficult to maintain...and could easily introduce errors. When you expect the Criteria Weight values to be very stable and you have good change management of rules, perhaps skip the…

It appears you have repeatedly changed your scenario. Which one of these applies: #1: Return work items which have one-and-only-one label, where that label is either "Customer-Experience" or "Operations". (In fact, none of the original work item examples you show in your question would match this case.) #2: Return work…

Hi @Dick Thanks for your article describing trading-off storage for query performance using automation. This technique may also help when the built-in features of JQL do not support the needed query (e.g. complicated date / time evaluation), using an "indicator" custom field for the desired condition. One risk…

Hi @Oliver Moore Currently, it is not possible to nest branches. And, because branches on more than one thing process in parallel and asynchronously, you cannot add another branch later in the rule to add the comments to the created work items. For your scenario, one possible work around is using the Send Web Request…

Hi @Artem Miroshnychenko -- Welcome to the Atlassian Community! You may want to ask this question in the Developer Community also: https://community.developer.atlassian.com/ Kind regards, Bill

Hi @Miriam Grühn That pop-up / prompt is a built in feature because you are using Subtasks...reminding the team to manage the status of the parent work item. The parent work item is selected in the Sprint and the child Subtasks are not, and so the reminder helps errors in managing sprint scope. I do not believe it can be…

Please show images of your complete Edit Work Item action and of the audit log details for the rule execution (with the areas at the right side expanded). I also recommend writing that entire JSON expression to the audit log before the edit to confirm it contains what you expect when the rule runs. Thanks!

Hi @Dave Stillwell For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution *…

Hi @Christopher Yen Jira Server / Data Center automation for the Lookup Issues action does not support custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 That action only supports a very limited number of fields at this time:…

That expression is not correct. An example to set that field could be: * trigger: some trigger, returning the Epic * action: lookup work items, with JQL to return the children of the Epic * smart values condition:* first value: {{lookupIssues.size|0}} * condition: greater than * second value: 0 * action: edit work item *…

To select just one of the labels do that with the JQL: project = XXXXX AND issuetype = Story AND status = Done AND labels IN (Customer-Experience)

Hi @Ethan After Jira UX changes, some things to try are: * refresh the page * log out and back in * log out, clear the browser cache, close all browsers, then open one browser and log back in Other than those, would you please confirm the configuration you are showing? It appears you have: * a company-managed project *…

For the first approach, I meant using something like the Filter Results gadget with a query specifically for one of the Labels. Then do not display the labels as the count (and perhaps gadget name) would indicate what is needed.

First thing: well done on the progress you made solving this! With conditional list filtering, we can filter at different scopes. And as you discovered, filtering inside of the {{#labels}}...{{/}} nested, long-format iteration conceals data from the higher, pages scope. (This is a known limitation the automation team has…

Thanks for that information, and... With the built-in dashboard pie chart gadget, there is no additional filtering to do that. Workarounds would be needed, such as: * Use separate gadgets which report one of the values at a time for the count (e.g., filter results gadget) * Use an additional label custom field, updated…

Hi @Mahesh -- Welcome to the Atlassian Community! A JQL expression helps search for work items / issues meeting the criteria. It does not impact filtering the specific values of fields shown in the results. What problem are you trying to solve by searching for work items containing those two label values but not show all…

Hi @Korbin Perry -- Welcome to the Atlassian Community! You seem to be using the term "document" and I wonder if you mean Confluence page... Are you planning to have a separate Confluence page for each week, and you want to copy some content from last week's page to the new week's page? If so, there are some upcoming…

Hi @Mehak Bokhari -- When are these changes rolling out? I do not see them noted in the weekly release blog or in the rule editor yet. Thanks!

The Re-fetch should be immediately after the trigger, not at the end of the rule: * trigger: Work Item Created * action: Re-fetch Work Item Data * action: Edit Work Item... Putting it there helps solve the problem of the work item being in an unstable state when the rule starts. After we solve this error, we can examine…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Just to confirm, did you remove the extra spaces from the JQL in the rule?

Hi @Carol Low Thanks to you and the team for these improvements. How do you see this impacting Jira Product Discovery (JPD) field configuration, particularly for the overlapping global fields? Kind regards, Bill

Hi @B Praveen Kumar Varma -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an…

Hi @Jack Brickey FYI -- The inline math expressions may not work for this case if the first value in the expression is an integer. That will lead to integer math being used for the remainder of the calculation...probably always resulting in 0 for this scenario. The long-format math expressions will instead use floating…

Hi @Amal Johnson You may do this with three different automation rules: * One triggered on Work Item created * One triggered on Field Value Changed, selecting all of your input fields * One contingency rule, disabled by default. This rule would use a Scheduled trigger with JQL to identify work items to update, and only be…

Hi @Mike Jones -- Welcome to the Atlassian Community! Without seeing the specifics of your rule and the audit log details... I hypothesize that because the rule branches over multiple pages and tries updating the same, specific page repeatedly, the updates are colliding and eventually causing an error. (Branches over more…

Hi @Louise Baker Where do you see a value of yesterday at 5PM? I only see your rule using the jiraDate text format, which is just the date as yyyy-MM-dd: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- Perhaps if you add an image of your audit log's details showing what…

Hi @Jeremy Schrek Both of the methods you show use branches which could find more than one work item. Branches of that type process in parallel and asynchronously, and thus any variables created inside the branch vanish after each item is looped over...and, there is no guarantee the branch will complete before the steps…

Hi @ajtritt -- Welcome to the Atlassian Community! Do you mean using the Object Created, Updated, or Deleted rule trigger: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Object-trigger Kind regards, Bill

The smart value {{destinationIssue}} only works when the trigger is one of the link-related ones, not for other triggers. Instead you would need to: * Use something like Lookup Issues to first find the Portfolio Epic, and then use that information to identify what is needed, or * Access via the issuelinks smart value and…