Bill Sheboy Expert

Hi @Conan Torres -- Welcome to the Atlassian Community! That is possible to do with an automation rule, however... What problem are you trying to solve by doing this? That is, "why do this?" That seems like a "push" rather than a "pull" approach to delivery, where the team will grab the next thing to work on when they have…

Thanks, and oops! That's what I get for typing stuff like this without trying it first, or using a code editor :^) I updated my first post so the initial one has your correction.

Hi @Thomas Urbanitsch -- Welcome to the Atlassian Community! I notice from the screen images you posted that this is a personal / private board, stored in your profile. It is not stored with the MP project you show. And, I just reproduced the result you observed. I have noticed several challenges / limitations with…

Hi @DJAMA Walid -- Welcome to the Atlassian Community! This is the Atlassian Community. It is a place for people with similar interests to learn and collaborate with one another. It is not the Atlassian Support team's response portal. If you need to contact the Atlassian Support team, please work with your Jira Site Admin…

Hi @Martin Vali As some recommendations to help with your future community questions... This is the Atlassian Community. It is a place for people with similar interests to learn and collaborate with one another. It is not the Atlassian Support team's response portal. Thus, community members will respond to posts /…

Well done! I almost suggested that approach, but erred on the side of removing any redundancy in the dynamic JSON building (and so extracted the "value" parts outside the conditional checks). I wonder: does your field contain any values other than "valA", "valB", or "valC"? If so, that could explain why my version did not…

Please post an image of the audit log details showing the updated rule's execution. That will indicate what happened when the rule ran. Thanks!

Please show an image of the audit log details for the rule execution, obscuring your site URL. That may provide context for what you are observing. Thanks!

Please post an image of all the audit log details for that run of the rule. Thanks!

Hi @Alex Yes, that is possible, and could be done outside of your iterator over the values. And there are several ways to do this... One inefficient way is... to use multiple calls to Lookup Issues, adjusting the JQL for each issue type, and then save each result's formatted output in a variable. Then check if that…

Hi @Mickael Maujean Some of the "epic" fields are sunsetting in Jira Cloud, so the "parent" field is used for the entire hierarchy to connect parents and their child issues: * epic* story, task, or bug* sub-task In rules, you will probably see the language change over time. For now, you can usually use them interchangeably…

Hi @VAlesbury Scenarios related to cascading date changes are challenging with automation rules, primarily due to the variety of ways issues can be "linked" and the execution service limits of rules. Starting with your second question first: I would also like a rule that changes all child tasks to match the due date of a…

Yes, I noticed you appear to be using Jira Data Center, and that should not matter for using the lookup results this way. Let's say you wanted to branch on JQL to all of the issues found for a lookup issues result. The JQL would be this: key IN ( {{lookupIssues.key.join(", ")}} ) That will create a comma-separated list of…

Hi @Mario Anthony Camillo -- Welcome to the Atlassian Community! I hypothesize this is a symptom of the intermittent type problems caused by each team-managed project (TMP) having distinct values for types, configurations, etc., leading to scope confusion in rules. The difference in behavior you see when the rule creates…

Unfortunately, you may not use the lookup table for this scenario either. The reason is once inside of an iterator, no other data is accessible from outside. And so when you iterate over customfield_67890's value the lookup table cannot be accessed. Instead you will need to use a series of conditional expressions. Let's…

As that error shows, there is also an error with the JQL for your Lookup Issues action. Please correct that to remove the stray quotation mark.

What happened when you tried testing the rule? What did the audit log show? Successfully using Jira Automation requires learning and experimentation, so please remember to test your rules (and their JQL). If you look closely at that branch JQL, and tested the rule, you will see the ending quotation mark appears to be in…

First things first: Successfully using Jira Automation requires learning and experimentation. When one just uses rules provided by others, whether from the community or Atlassian templates, without understanding the rules, one will be unable to maintain and improve them. I have provided several references to help you pause…

Hi @Cedric Devaux 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.…

Please post a screen capture showing Phase as an issue type. That is not a built-in / default one for Jira Cloud.

Thanks for clarifying, and I was noting the duplicated JQL expressions in each of the condition and branch, not that it was used in both. That still seems to be a thing, based on what is shown in the audit log :^) Scenarios like this are often problematic because the Summary field is being used to store multiple pieces of…

Thanks for that information, and there are several cases to handle. Let's start with a basic one: * trigger: issue field Epic Type changed * condition: issue type equals Epic * branch: to child issues of the Epic* action: edit issue, copying the field from the trigger issue The other cases will need additional rules. I…

The JQL for you branch is missing the quotation marks around the project name. Please add those and then test your rule. And...with the Issue Created trigger, I recommend adding the Re-fetch Issue action immediately after the trigger. That can prevent timing problems as that specific trigger can fire so quickly that some…

Backing up a bit...as something appears to have changed since the last time I tried this scenario a few years ago. Now this: {{issue.description.text}} Will lookup and replace the mentions with the users' display names. However that will also remove all formatting from the field. If you need to preserve the formatting...…

In that case, your custom field (for display in Miro) should be set based on which value you want to show, and there should be no need for the advanced edit with JSON: As a number of seconds: {{issue.timetracking.originalEstimateSeconds}} As a human-readable, pretty printed, calendar / time…

@Khira Niemeier -- Please review the article where is shows entering the Header information for the request.

Thanks for that additional information, and... There appears to be duplication in your JQL where these expressions are included twice: issuekey IN childIssuesOf("ABC-1234") AND issuetype = Story and summary ~ " Readiness" I suggestion removing the second instances of those in the JQL to help diagnosing this. Next, I wonder…

Hi @Rafael Pessoa -- Welcome to the Atlassian Community! What you show will not work with the Due Date field: as Trudy describes that field is a date field and does not have the resolution of date / time. With an automation rule, there are two ways I can think of to gather the cumulative time an issue was in a flagged…

Hi @Seenivasan K There are lots of open suggestions to add this capability, including this one you may watch / vote for to see any progress: https://jira.atlassian.com/browse/JSWCLOUD-25443 Kind regards, Bill

Hi @Sean C-S -- Welcome to the Atlassian Community! To clarify your scenario a bit, are you trying to copy values from one multiple-selection option field to another multiple-selection option field, perhaps translating the values in the process? If so, your rule cannot use a branch to do so. The reason is branches which…