Bill Sheboy Expert

Thanks; this helps to isolate the cause a bit. Just to confirm, when you use that JQL with the REST API call for an issue search, does your example story 1898 show all the expected sprints 1, 2, 3, and 4 in the returned sprint data of the response? You could really isolate this if you temporarily add that specific issue's…

Well done solving this! FYI -- The {{triggerIssue}} smart value is always the trigger one (when there is one for the specific trigger used) and {{issue}} can vary based on context within the rule. To learn more, please see this article where I describe this difference:…

Hi @Luka Recine -- Welcome to the Atlassian Community! There is almost no publicly available documentation on this Premium / Enterprise license feature of automation rules: https://support.atlassian.com/cloud-automation/docs/advanced-automation-components/ I am not using either of those license levels, and cannot…

Thanks for your article, @Rachel Wright Yes, and...I wish the workflow editor had organize / layout / validate features to help. It seems the guidance from Atlassian is to create / plan non-trivial flows outside the tool and then draw them inside. Kind regards, Bill

Looking at the log you show, your rule uses the Edit Work Item action. When you write the "after value", is that from the field? If so, the edit only updates the value stored in the Cloud, not what the rule has in memory. Please add a Re-fetch Work Item Data action after the edit action, and before the comment and write to…

Thanks for that information, and please try to stay with one thread when responding. That will help people reading this question in the future know if there are multiple possible solution approaches. Thanks! FYI -- the closedSprints() function only indicates a work item has a value in the sprint field for a completed…

Hi @Katie Kusjanovic 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 Until…

Hi @AjayShankar AN Would you please clarify how you are searching for those work items? Specifically, which endpoint are you using? For example, are you doing one of these: * Calling the Search for issues using JQL enhanced search endpoint, passing JQL that uses the closedSprints() function, and then filtering the results…

Hi @Aline Veyradier Short answer: the built-in features of Jira automation rule actions do not support most of the macros for fields such as Description. There are complicated workarounds using the REST API endpoints. Another option is using a marketplace app for checkbox handling as some of those can be set / updating…

Thanks for that information, and... When you note this: If I run the automation as scheduled trigger and filter for key=A123 then the rule doesn't work. I am wondering if I am using the correct Copy from process in the scheduled trigger flow. What do you mean "the rule doesn't work": the audit log shows an error, or no…

Hi @Dave LIAO My understanding from other community posts is the JPD project's work items are not publicly visible, and so this suggestion may already be in there and we cannot see it :^) We can only make suggestions from within Jira with feedback under ? -- Help and from community posts like this one from Kelly. Kind…

Hi @Marc -Devoteam- FYI -- Andrea cannot accept your answer as they are not the original poster of the question in this old thread. Kind regards, Bill

Ah, you added the prefix text I put on the number calculation. For example, "Current Score: " When setting the number value in the Edit Work Item action, only include the math expression, such as: {{#=}}0{{issue."Weight %"}} * 0{{issue."Current Maturity Level".value.substringAfter("L")}} / 5{{/}} . 

Hi @Mikel Whipple I see a few things to check in the rule images you show... First, the Edit Issue (or Create Issue) action may only update a field one way in a single action: with the field dropdown list or with JSON. You have selected both. Please remove the field from the dropdown list, update your rule, and re-test.…

Hi @Ashok gunampalle -- Welcome to the Atlassian Community! There was a production incident yesterday for this symptom, which has since been resolved: https://jira-software.status.atlassian.com/incidents/z1hkqr6lyyrq I recommend trying the upload again, and if it fails...please ask your Jira Site Admin to submit a defect…

Hi @Matt Doar _Adaptavist_ Thanks for the feedback. I corrected that one and another error I made in the text. Kind regards, Bill

Hi @Dave Stillwell Have you confirmed that ScriptRunner JQL function works with automation rule, Scheduled triggers? Are all of the issues in the same project or in multiple projects? If in other projects, what is the scope in the details at the top of the rule? Kind regards, Bill

Hi @Kaviyasri S -- Welcome to the Atlassian Community! Yes, and...to the answer from @Trudy P Claspill You could also create a saved filter and ask person ZZZ to subscribe to the filter on a cadence of their choice. The JQL for the filter could find just Bugs assigned to user YYY in that project within a specific…

Hi @Vitalii Rybka In my opinion, there are no best practices; there are only better or worse ones for a specific team and the current context. And thus... Please consider what your team means by "technical debt", and more importantly, how you explain the cost / benefit of those work items to the people who prioritize work.…

Even when the lookup returns one issue, that still produces a list-of-lists. One way to confirm that for your rule is inside the branch, write this to the log as the first step: teamComp: >>{{teamComp}}<< If the values are iterated as individual displayName values, each one will have that prefix and be surrounded by those…

You could try emailing the community managers to learn how they might put you in contact with the Atlassian Support team to learn next steps: communitymanagers@atlassian.com

Awesome; I am glad to learn it is working now! For a custom fields with structure (e.g., select-option, user, version) they have different attributes. For user-selection fields, those include the accountId, displayName, emailAddress, etc. When a custom field is referenced in a rule as just this: {{issue.customfield_12345}}…

Hi @Sai Seelam -- Welcome to the Atlassian Community! First, I recommend creating a new question with the "Ask a question" button at the top of this page. That will help focus on the specifics of your question. When you do so, please include images of your complete rule, the audit log details, and explain what is not…

Ah, a lists of lists problem! Short answer for the fix is change the branch's smart value expression to use flatten and distinct. {{lookupIssues.customfield_11610.displayName.flatten.distinct}} More information... Inside the lookup results, each work item has a list of values in the multiple-selection, user field. When…

For more context, please post images of: * your complete rule, * the rule action where you try to update the field, and * the audit log details showing the rule execution

Hi @Jordan Dowdy Even with your description of the steps, perhaps more context will help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches…

Hi @Lindsay Kirsch With the current features of Confluence automation, I suspect your rule would need to: * call the REST API with the Send Web Request action to get the page content, and * extract the value(s) from that macro's data using text functions Kind regards, Bill

Hi @Bernadett Sándor That knowledgebase article is missing guidance that you may want to add to a rule... What if the calculated Start Date is in the past when the estimate is subtracted from the "Due Date"? This is a common problem with automated, backward-planning scenarios. With that KB article, I recommend not editing…

Hi @Qedi Testing -- Welcome to the Atlassian Community! I believe those old Greenhopper endpoints are unsupported now. And as they apparently used the issues' history to calculate those measures, two alternatives are: * Investigate marketplace apps which can do this, also using the histories * Use automation rules and…

With the Scheduled trigger, you can optionally add JQL so the rule provides work items to process. Your rule is missing that JQL and so the errors appear. Please add JQL to the trigger for the work items for which you want to update their parents.