Bill Sheboy Expert

Hi @Darryl Lee Thanks for your kind thoughts and the summary list. To find my other ones (which appear to have some duplication over time :^) you may look within the automation articles with this search. Kind regards, Bill

@Darryl Lee there are several ways to remove the first item from a list using smart values, including using the {{^first}} ... {{/}} handling once inside of the long-format iteration. For example: {{#varList.split(",").trim}}{{^first}}{{.}},{{/}}{{/}} Notice this will add each item after the first one with a trailing…

Hi @Darryl Lee -- how about a maybe #7 approach: Using the Bulk Create Issue endpoint, use list iteration over a lookup result for the linked work items to build the JSON message, and try adding them with one Send Web Request. I could not find information if the items are iterated to add sequentially or in parallel, so…

Hi @Darryl Lee Until a sequential branching feature is added to rules, there are a few workarounds, each with their own cost / benefits / risks. Some of these will not work with linked work items, but I will list all the ones I can think of regardless. Some shared risks for the workarounds are: * although there is an upper…

Hi @Ryan Hormann Link types are directional, and automation rules trigger on a specific work item in one direction...regardless of from which work item the link was added. (To learn more, please see this post from @Trudy P Claspill ) And thus, please check your link type configurations to confirm which one is going to be…

Hi @cvanduyn First thing...Although I understand why you are fully elaborating your workflow into status values and board columns, in my experience, Jira is not a good tool for using a board with more than around 5-6 columns. It does not have features to collapse / expand columns and manage longer flows like other such…

Hi @Leslie Hicks Are you using a team-managed project (TMP) with its People custom field type? If so, the email address is not available within rules: https://jira.atlassian.com/browse/JSWCLOUD-27793 I recall the possible workarounds are: * read the user with the REST API endpoint and the Send Web Request action to get the…

Hi @Tejas Patil This may be done by creating two lists of components, finding the overlapping values, and finally using list iteration to build an advanced edit with JSON expression to add the desired components. Please see this article I wrote describing how to find the overlaps between two lists of items:…

Hi @_Ekta Lala You are creating the Idea and so the linking is in the opposite direction: "is implemented by". Please try these steps, with some changes to prevent other potential problems: * trigger: Work Item Created * action: Re-fetch Work Item Data * fields condition: Issue Type equals Epic * action: Create Work Item*…

Thanks for that information, @Amy Everitt When a rule shows errors like this for smart value expressions, I recommend adding some log statements for each of the field values. That will confirm they contain what you expect when the rule runs. You may use the Log action to do this. Next, I suspect your field's smart value is…

Hi @Kenn Roberson -- Welcome to the Atlassian Community! Yes, and...to the information from @Mikael Sandberg Here is the suggestion to add that trigger to Jira software space rules for their form type: https://jira.atlassian.com/browse/AUTO-1661 Kind regards, Bill

Hi @Darryl Lee Seems like a good solution approach to me! Respectfully, my suggested improvements to your rule are: * With the known racetrack timing data defects in triggers like Work Item Created, mitigate those by:* Add a Re-fetch Work Item Data action immediately after the trigger * Never use the new feature to add…

Hi @mike There is no easy, built-in way to do this, and... Issue links typically have a direction, such as with ABC-123 --> "blocks" --> ABC-456, while the opposite direction is "is blocked by". Thus, when cross-linking as you describe for the three issue scenario, the link types could quickly become complicated, or worse…

Hi @Tim Gesner -- Welcome to the Atlassian Community! One possible cause of the symptom you observe is the known, racetrack timing defect with the Work Item Created trigger. That is, the work item data is not consistently available when the rule starts. The mitigations for that are: * Immediately after the trigger, add a…

Hi @Artur First thing: when responding to suggested answers, please try to stay with that thread. This will help people reading the question in the future know when there are multiple solution approaches. Next, the question of how to extract mentioned users in a comment and add them to a multiple-selection user field has…

Hi @Aldrine Abisheck -- Welcome to the Atlassian Community! Are you trying to measure time-in-status or working time? * For time-in-status, try the built-in reports (e.g., control chart) or the better ones provided by Atlassian Marketplace apps. * For working time, try the built-in time-tracking features and reporting, or…

Hi @Jeremy Jones I am glad to learn you found a workaround, and... There are known racetrack timing defects with the Work Item Created trigger. This means the work item can be in an unstable state, with incomplete data as the rule starts leading to weird errors and missed conditions. In some cases, the work item does not…

Hi @Amy Everitt First thing: your field name "Target Date" is very similar to the names of a couple of built-in fields. Please use caution to ensure you access the correct field, perhaps using the custom field ID within rules. Next, Jira Product Discovery (JPD) uses its own date format with JSON represented as text,…

Hi @Anurag Chavan While one could create a single automation rule to accumulate the time in the status, it may be unreliable for several reasons. Please consider these when using a rule for status tracking: * When rules exceed the service limits, they do not run; thus, the time will be missed * When Atlassian has an outage…

Hi @Lisa Mendonsa Have you tried using the substringAfterLast() function? https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringAfterLast-String-separator- Kind regards, Bill

Based upon that image, the field is not used in any spaces. Is that correct?

Which Confluence REST API endpoint are you calling with the automation rule?

Hi @Aldrine Abisheck Trying to solve work in progress (WIP) limit concerns in an automated manner with tools may lead to unintended consequences. Two such consequences could be: * Team members may stop updating work items in Jira and do the work anyway. Thus, work progress and WIP become hidden, and as this behavior…

Hi @Mitchell Dyer -- Welcome to the Atlassian Community! Which Confluence REST API endpoint are you calling with the automation rule? Have you tried calling the endpoint with an external tool or browser to confirm it is well-formed? Within the rule and the Send Web Request action, if you use the Validate option near the…

Hi @Jeremy Jones Do you have multiple fields with the same name in different scopes (e.g., global / company-managed and local / team-managed), and is one of the work items showing errors in a team-managed space? If so, this symptom can occur when the rule processing uses the incorrect field due to the rule's global scope.…

Hi @_Ekta Lala Please see the information provided by @Kamila Czubaj for more information about the Polaris link type. Unfortunately, that type in the UX appears as "implements" and "is implemented by"...which is the same as another link type. Thus, using the Polaris information or "implements" AND the work item types is…

Hi, @Trudy P Claspill A quick test showed me the inward and outward link type names are not available with Lookup Work Item Data in the issuelinks smart value (which I should have guessed as some linked data is found just-in-time :^). Thus, an adjustment is needed to my suggestion...we need two lookup calls: * trigger:…

Hi @Matt Brescia -- Welcome to the Atlassian Community! When date or date / time-picker fields are used as a smart value, they can implicitly return a date / time value...even when they are only for a date-picker. (For date only, the time returned is the start of the day.) One workaround for this is to force the value to…

Hi @Aroney -- Welcome to the Atlassian Community! This may be done with a Jira Automation rule... You describe duplicating the page on a specific schedule. Is that aligned with your sprint creation or starts? If so your rule could be triggered on Sprint Created or Sprint Started, and then use the sprint name to build the…

Hi @_Ekta Lala Short answer: that cannot be done directly. Jira Product Discovery (JPD) fields for delivery progress, calculated fields, etc. are only displayed in the UX and are not saved with the Idea. A workaround for some of these fields is to dynamically re-calculate the value in an automation rule. For delivery…