Bill Sheboy Expert

Recalling that thing I mentioned about branches, scope, and "most recently created"...your second branch likely cannot work because the rule cannot "see" there was an issue created. What is happening in that last Edit Issue action? Could the changes be done at the same time as the cloning, which would eliminate the problem?

Awesome; progress! That error can be caused by a several things. Let's check them in order of likelihood: * Rules can get "glitched" by too many edit/publish cycles. I do not know why this happens* Checking this:* Disable and re-enable your rule, and re-test * If that does not help, disable your original rule and re-create…

Thanks for that information, and please try to keep responses to one thread. That will help others in the future know if there are multiple solution approaches. Thanks! Your rule is triggered on Issue Transition and then trying to access the {{pullRequest}} smart value. That smart value is only available with the…

Awesome; I am glad to learn that helped!

For Jira Cloud there is an action for Create Variable, that allows saving the key for the newly created issue for later use. That can work-around the scoping issue for if/else structures. Back to your rule: when you not the value update is not working, what is happening? Would you please post an image of your new, smaller…

Thank you for clarifying that you are using issue linking rather than parent/child issue relationships. Are you using a Company-managed or a Team-managed project? You may find that information at the lower-left side of the page expanding area. This is important because Company-managed projects use the "Story points" smart…

Hi @Thibaut LEGRAND -HONGQIAO- I am adding to Trudy's ideas and jumping in to try to help... Looking at your current rule, I see some issues and want to suggest some things to try: * You first noted you have a rule that correctly sums Subtasks to Tasks. And now you want to sum Tasks to their Epic parents. Yet your rule is…

Thank you for all of those details, Mary! That is a complex rule, that I suspect is not working as you intended...due to a couple of things. First, rule branches which could be on more than one thing (e.g., on linked issues, on subtasks, etc.) are processed in parallel and asynchronously, relative to the rest of the rule.…

What you describe is not default behavior; please clarify how you are using Jira issue types. This may be a case where you are using terminology which does not match Jira. The default issue hierarchy for Jira Cloud is: * Epic* Story, Task, or Bug* Subtask And so an Epic can optionally have child issues of Story, Task, or…

Hi @Hrvoje Dolenec I suspect you could do that with an Automation for Jira rule, for a specific project's issues, within the current iteration / sprint. Looking at a larger scope may not work because of the limitations for rule execution. Also please consider: "estimates" are estimates, and so any reporting would also be a…

Pausing for a moment, if you run a stand-alone query in View All Issues with the following, what do you observe: parent = NG-443 AND remainingEstimate > 0

Hi @Brian Rhodes -- Welcome to the Atlassian Community! First thing, I am just another user trying to help by answer questions. I am not an Atlassian or marketplace vendor employee. The drag-and-drop feature to order issues in Jira is based on the Rank field, as you noted. That spans all projects (and issues) in the…

Awesome! On to the follow-up questions... For some context, please post an image of your complete automation rule in one image. You can do that with a screen capture tool, or browser addon which does scrolling page capture. If there are any issue create or edit actions, add separate images for those. Then post an image of…

Do you see the typo in the Lookup Issues JQL, where there is a space after the curly bracket? That may be evaluating to parent = null... Please try removing that extra space.

To help see the big picture, I recommend using either a screen capture tool or browser addon so the entire rule can be captured in one image. And so I am guessing a bit from some of the posted images showing the rule in pieces. In the action where you create the issue (i.e. Task), the Epic Link is set to "Copy from Trigger…

Yes: the alternatives which I already listed above.

In that case, I believe you would need to use advanced edit with JSON rather than the basic field edit. The syntax for updating that type of field is shown here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field And so you would de-select Roadmap owner from…

Thanks for posting your rule images. You are trying to use ScriptRunner functions in the automation for Jira rule to sum the values, and I do not believe that is possible: automation rules do not understand things like aggregateExpression(). I recommend checking the ScriptRunner documentation if you want to try that…

Hi @Phil Beckman Yes, and to Trudy's answer... That change to the packaging model describes which actions count and do not count for the new limits...And conditions do not count (as of the time I am posting this :^) Thus you could reduce your usage count by adding conditions to test if Program and Time Classification have…

Hi @Kaylen Davis -- Welcome to the Atlassian Community! First thing, I am not using Zendesk Support, and so my answer is based on my understanding of automation rules. With that disclaimer out of the way... Your scenario confuses me: if the trigger is Issue Created, why would the issue be in a status of "completed" at the…

I wonder...should the JQL test if the remaining estimate > 0 rather than just not empty? A 0 value would appear as "not empty".

Hi @Kelly Hansen -- Welcome to the Atlassian Community! Where is your list of values located? If it is in a smart value / list, you could use the Advanced Branch feature: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 Please note: this type of branching…

What type of field is "Roadmap Owner"? If that is a user field, you cannot store a text value from Project Category there.

First thing, in which post do you want to work on this symptom: this one or the other post? Knowing that will help focus the community conversation, and you can close out the other one (if it is a duplicate). Thanks!

Hi @Hasmik Hovhannisyan I recall from other, similar posts the state attribute, return value was lowercase (or different than what was shown in the documentation). Without seeing your entire rule and the audit log, I wonder if that is the cause. You may confirm this by writing those smart values to the audit log prior to…

Hi @michelle.purcell You did not post your entire rule, yet from what I see...there is a condition on Issue Type equals epic. If that is the trigger issue, it will not have an epic link, and so this rule could never have worked that way. Please post your entire rule, and the audit log details showing the rule execution, to…

Hi @Valmira Bixhi -- Welcome to the Atlassian Community! What value are you trying to store in the Roadmap Owner field? The smart value {{issue.project.projectCategory.name}} is the Project Category value, not a user. Kind regards, Bill

Hi @Ran Wronsky 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.…

Great! Now you have a template to create your 16 test cases (assuming the numbers have values) or 128 (assuming the numbers are empty or filled). I recommend pausing to create those before updating your rule. As long as those "numeric tokens" are not used the "any text after", you could use the replaceAll() function I…

Hi @Sridhar Gandla Would you please confirm you are using Jira Server, and not Jira Data Center (or Jira Cloud)? If you are using Jira Server, you will not have the Lookup Issues action which Matthias describes. Instead you could either user the bulk-handling feature of Jira Server automation, with the {{issues}} smart…