Bill Sheboy Expert

Greetings, Community! I recall @Hana Kučerová asked a variation of this same question a couple of days ago. Please look here to see suggestions in that thread: https://community.atlassian.com/t5/Watercooler-discussions/Three-wishes/td-p/2891146 Kind regards, Bill

Hi @Emily Ashley The rule will not be able to do that with branching because the Edit Issue action acts upon the issue currently in context...and that would no longer be your trigger issue. Instead you could use the Lookup Issues action with JQL to find the relevant Initiative for the trigger issue and then copy the field…

Hi @Raycher There is a format of the conditional logic which supports nesting: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if {{if(smartValue, "value if true", "value if false")}} Thus for your case, it could be this: {{if(customfield_1.accountId.isNotEmpty(),…

Hi @shantanu behera -- Welcome to the Atlassian Community! Yes, and...to the suggestions from @Trudy P Claspill Although there are several variants of Kanban which use iterations and planning cycles (e.g., Kanban Method), there are often other measures which help to observe flow, delivery progress, and guide the team in…

Hi @Bentley_ Andrea That is not possible with the current features, and here is a related suggestion to add defaults to the user input options: https://jira.atlassian.com/browse/AUTO-744 As a workaround, you could copy the input field to a variable when it passes a condition, and substitute that with your default when it…

Hi @Nico I recommend using a Lookup Table for such mapping scenarios: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 With that, your rule would reduce to only a few steps rather than conditions for each group: * action: issue created * action: re-fetch…

Hi @Radu Ichim Short answer: in my opinion, a rule like this could be quite risky and perhaps the teams could instead investigate how to prevent adding those issues rather than deleting them with an automation rule. Back to the specifics of your question... First, you appear to be using Jira Cloud. Is that correct? If so,…

Hi @jodywhite For a question like this, I recommend posting images of the two reports / charts where you have identified differences for the same sprint. Those will provide context for the community to offer suggestions. Next, what do you mean by "variance"? There is a statistics definition of that term, and the equation…

Hi @Iain Powrie -- Welcome to the Atlassian Community! This is a long-standing limitation of automation rule iterators: only information at the iterator scope, and lower, is visible inside. Here is an open suggestion to change that behavior: https://jira.atlassian.com/browse/AUTO-490 For this scenario, the possible…

There is no built-in trigger to do what you ask. You could investigate using an Incoming Webhook Trigger if your source control / pipeline tooling allows calling one when the Request changes. Please note well: when asking an automation question, supplying an image of the automation rule and audit log details are essential…

With the complexities of this rule, I recommend not trying to also copy Components from the newly created issues. Instead add them again.

It appears you have saved the rule, but it is not appearing on the page. Please try refreshing the page to see if it applies the formatting. If it does not, and you are on a paid Jira license, you may want to work with your Jira Site Admin to contact Atlassian Support to ask them to…

If there are never any remaining incomplete issues in a sprint when the sprint completes, there will be no problem. But if there are incomplete issues... Here is the scenario I am describing... * Sprint 1 contains stories ABC-1, ABC-2, and ABC-3* Sprint 1 starts, and JQL checking sprint IN openSprints() will return all of…

Well done solving the last part! There can be challenges when mixing date math and time tracking values in rules... People normally enter time tracking as a "working time" forecast. When performing math on values such as Original Estimate, Jira uses its definition of "working time" only for logging time and pretty…

Hi @Radl Glück -- Welcome to the Atlassian Community! Adding to the suggestions from @Jack Brickey ... How many issues would you expect for these counts? Do you want to count all of the issues in the project, in a sprint, matching some specific JQL, etc.? These questions are important as the Lookup Issues action can only…

Hi @Angelo Fiore -- Welcome to the Atlassian Community! A couple of FYIs that may help regarding the automation match() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- 1) Only the first matching group is returned, and thus more complex regular expressions may not work.…

Hi @Lukas Hametner That error is indicating the condition needs an issue, and there are none available at that point in the rule. This is likely caused because your Scheduled trigger has no JQL, and so supplies no issues. There are two possible solutions for this: * Add JQL to trigger to find the issues to process, perhaps…

Hi @vincenzo.spatafora You are correct the Jira Data Center version of the Lookup Issues action only supports a limited number of fields at this time. There are two possible workarounds, depending upon your rule needs: the bulk-handling feature or calling the REST API endpoints. Please look here to learn more about these…

Hi @Rebekka Heilmann _viadee_ Thanks for your article. In addition to 5-whys and other root cause analysis (RCA) methods, please consider "Job Shadowing" or "Pair Programming" methods to learn more about how team members use (or do not use) Atlassian tools to help them deliver value. By either observing (or guided-doing in…

Hi, @Hana Kučerová Thanks for the prompt! My three would be: * Product Management and Engineering could invest the time and analysis to finally clean up the entire public backlog, consolidating duplicates, and honestly closing suggestions / defects in a timely manner which Atlassian never plans to address * Reverse the…

Hi @Nguyen Thanh Tien Based on the rule image you show, there are several ways to do this: * Use a simple smart values condition to check if the get() call returns anything, and only then perform the edit. This approach will only perform the edit when needed. * Use an inline condition with the format {{if(smartValue,…

Hi @Nikki Colletti After your rule clones the issue, you could branch to it to transition it. Another option is to call the REST API endpoint to create the issue and set the status at the same time, although that would make copying the issue fields (for cloning) much more complicated. If this does not help, please post…

Hi @henry_lin -- Welcome to the Atlassian Community! For Jira Data Center, the Lookup Issues action does not yet support the Comments field: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-lookupissueslookupIssues https://jira.atlassian.com/browse/JIRAAUTOSERVER-877…

Hi @Jon Hays -- Welcome to the Atlassian Community! Scenarios like this with automation often require two steps due to the way smart values like the web response are parsed: * first extract the value from the web response, and store it with a created variable action * use the variable, converted with asNumber, and then…

Hi @Hammad Shami -- Welcome to the Atlassian Community! That article is for the Jira Data Center version of automation rules. There is no secrets manager for the Cloud version yet, and here is a suggestion to add it: https://jira.atlassian.com/browse/AUTO-1365 Kind regards, Bill

So is the trigger issue an Epic? If so that may simplify things a bit: * trigger: manual * condition: issue type equals Epic * condition: Component equals PBCA EPIC * action: create issue (1st one)* set the Epic Link to Trigger Issue or {{issue.key}} * copy the Components from Trigger Issue * action: re-fetch issue *…

Thank you for that information, and... The smart value to see the entire webhook response message would be: {{webhookResponse.body}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--webhookResponse-- And for that REST API endpoint to get the list of versions, I believe you want this smart…

1. Does this mean that I need to remove all branching? Answer: Correct, the branching is no longer needed. It only helped with the linking and that now works. 2. I have a list of about 15 tasks that my complete automation runs, does this mean I need to keep track of the index for each one that I want to link to and adjust…

To confirm, what version of Jira are you using: Cloud, Server, or Data Center? Assuming you are using Jira Cloud, please see my earlier post above as the branch is not needed: instead use lookup issues action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues Following the rule…

Hi @John McCann -- Welcome to the Atlassian Community! As this is an older thread, I recommend creating a new question, and perhaps adding a link back to this one. That will ensure the maximum number of people see it to offer suggestions. When you post your question, please describe: * How prioritization happens for your…