Bill Sheboy Expert

Hi @Stewart_ Emily _ Global D_T There is no automation list sort function, although there is an open suggestion to add that function. For your scenario: GIVEN an issue with multiple-select, user picker custom fields: "UC Approved By" and "UC Approver" WHEN "UC Approved By" changes AND the selected values in both fields…

Hi @Joe Riley -- Welcome to the Atlassian Community! Short answer: this scenario cannot be solved using rule branching, and so a more dynamic-search method or chained-replacement is required to sum the fields. Here are details on why branching and long-form iteration will not work, and some workarounds... Rule branches…

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

Hi @Mohanraj Thangamuthu I believe the Community Managers can move the question to the other location, so please ask them to do so. Thank you! Kind regards, Bill

Hi @GPT AddIns Whenever I see a question / post requesting a feature for multiple assignees for a single Jira work item, I wonder: what problem is one trying to solve? For example... * Perhaps the "team" is actually composed of sub-teams, and there is a desire to assign work items to the members of a sub-team so they get…

Seeing your actual rule will help to fault-isolate for any other possible causes. For example, even that simple case based on the help / documentation could fail when the lookup results are empty. And, to read what others have encountered with that new rule action, please see the article which first announced it:…

Hi @Ryan Saul -- Welcome to the Atlassian Community! 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…

Hi @Parto Hamidi Short answer: I recommend breaking down this problem into pieces, and using created variables to help. There are several reasons why that expression cannot be done in a single step, and there is an error / typo in the JSON... A simple JSON expression to set the assignee this way would be this: { "fields":…

Greetings, Community Managers! Please move this vendor marketing post from this product area to to the App Central discussion group: https://community.atlassian.com/forums/App-Central/gh-p/app-central Thank you! Kind regards, Bill

Ah, yes...this is a known limitation of the JQL branch: it automatically excludes the trigger work item to prevent accidental endless loops. Essentially, it adds a clause to the branch JQL behind the scenes: AND key != {{triggerIssue.key}} As you also want to update the trigger work item, please add another Edit Work Item…

Although you could use what I described to remove the active sprint, have you considered inverting this symptom to align more with Scrum practices: * The team identifies the work / value they can deliver in sprint planning, and assigns it to their sprint * At the same time, they could add their team indicator to the custom…

Hi @Bharat Kalia What problem are you trying to solve by doing that edit? Knowing that may help the community offer improved suggestions. Until we know that... The sprint field is a list of values, and so may be iterated and filtered. Thus, you could filter on the state attribute to return the non-active ones and then…

I do not believe you need a lookup table. Instead, I was suggesting to used the Lookup Issues action: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-lookup-issues Using the {{lookupIssues}} result, iterate to create the page content, and then store that with a…

Hi @arielei Without seeing the specifics for your rule context... * Let's assume the rule trigger is Version Released * With that information, the rule could use the Lookup Issues action with JQL to gather the issues in the version * Then iterating the work items could be used to build the page content, storing the result…

Hi @Raschid Abdul-Nour What do you know about that specific parent? For example, if there is a specific work item key, you could add a smart values condition: * smart values condition:* first value: {{issue.parent.key}} * condition: equals * second value: ABC-123 Here I added an example key for the parent to compare. If…

Hi @Tim Bonney For a question like this, context is important for the community to help. Please post the following: * which REST API endpoint are you calling * 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…

Have you tried adding the Edit Work Item action, selecting the Sprint field, and then from the dropdown selecting the active sprint? Only when this rule is generic to multiple projects would you need to use the REST API endpoint (with the Send Web Request action) to get all possible sprints for the target project, and then…

Following what I stated, the rule could look like this: * trigger: value changed for sprint (with your conditions added) * branch on related work items: selecting the JQL option and using the JQL you currently have in the lookup...adding the condition to check the Fix Versions field: sprint = "{{issue.sprint.name}}" AND…

Hi @Bohumil Klimek -- Welcome to the Atlassian Community! The purpose of the Lookup Work Items action is to gather work item data as a batch, such as for summing on a field. It does not allow accessing the items as work items for edit. And so when your Advanced Branch iterates over the data, it cannot access the actual…

I am glad to learn that helped. And, if your rule is working now, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Frank Brundage What does not work as expected? Are the child Stories (presumably of an Epic) in the same project or in different ones? When they are in different projects, the rule scope (in the details at the top) must be changed by your Jira Site Admin to span the needed projects. Also, would you please post an image…

Hi @Oscar Santillana -- Welcome to the Atlassian Community! The symptom you describe is a long-standing limitation of automation rules: Inside of a long-format, list iterator, only information from that level (or lower) is accessible. Thus, your created variable cannot be "seen" inside to perform the filter. The Atlassian…

Hi @Eduardo Lima Boucault -- Welcome to the Atlassian Community! I do not believe automation rules currently use the version of the REST API which allows setting the status when the work item is created. Instead, rules need to branch to the newly created issue to transition it. For example: * trigger: some rule trigger *…

For rule limit uncertainty, I recommend being proactive and contacting Atlassian Support directly to ask them what is happening: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to benefit the community. Thanks!

Hi @Nadia Burborough Where are you seeing that notification pop-up? For example, from the rule list, admin functions, etc. Have you recently removed one (or more) Atlassian products such that it will lower your automation usage limits? I have not see that message, and I did not find any related announcements in the…

Hi @Trena Norcia Short answer: that is not possible with built-in features unless using a "bug subtask" work item type with the Story as the parent. A workaround to show the Bug / defect below the relevant Story, but without the nesting like subtasks, is to re-order the Bug using either drag-and-drop or the REST API to…

Thanks for that additional information, @Olesia Zhukova As this point, I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to take a look. You appear to be on a paid license, and so your admin can do that here: https://support.atlassian.com/contact/#/ When you hear back from them, please…

Thanks for those rule images, @Thermal Developer Some errors in the audit log do not always indicate the root cause(s) of the problem, and I see a few things to adjustment to help your rule: * Unless specifically necessary, I recommend leaving the Actor as the default of the Automation for Jira user. Please change that…

That seems odd... I know the UX does not always update immediately, often requiring a page refresh. But I have not observed a requirement to start the sprint before the items to show.

Hi @Thermal Developer -- 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 image…