Bill Sheboy Expert

Hi @Søren Hansen 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.…

Hi @Manel You appear to be using a Team-managed project, and unlike Company-managed boards, transitioning the issue will not move it to the board. An extra step is needed (manually or in a rule)... For a rule, you may use the specific rule action for Move Issue to Board. Kind regards, Bill

Hi @Thomas Franek -- Welcome to the Atlassian Community! One key for a scenario like this is state management. I recommend initially writing this as two rules, and then considering how / if to merge them, ordering the cases properly. You describe already having the first rule to send the reminder, and that probably uses…

Hi @Benjamin Buchwald Yes, and...to Walter's answer: I recommend discussing with people why they are doing this, even when advised not to do so. Perhaps there is a root cause problem / need which could be addressed and eliminate the problem (and the notification). Kind regards, Bill

Hi @Mary Mark Reviewing what you posted, I have questions and comments... What problem are you trying to solve by cloning issues and then immediately closing them? Knowing that may help the community to offer alternatives. Thanks! Regarding your rule structure, branches which could be on more than one thing are executed in…

In my opinion, the racetrack effect is a design problem / result of how the automation engine uses of the REST API functions. I have found no open defects for this in the public backlog, although I have suggested that Atlassian fully document which issue fields are set in two steps when issues are created / cloned: * issue…

Hi @Sheik Mubarak First thing: as this is an older thread, I usually recommend creating a new question and adding a link to the old thread. That will ensure more people see your question to offer suggestions. Back to your question... For your version of automation rules, there are two possible ways, depending upon what you…

No problem; re-reading your original problem, you will not need created variables... I am assuming you want the Story as child of the created epic, not just linked to it. Please adjust accordingly to meet your needs. I am also assuming that all of the issues are the same project. If not, adjustments may be needed. Let's…

Hi @Dash_ Karrie Contractor I am using Jira Cloud, not Data Center, but I wonder...have you tried using issueLinkType, perhaps like this: issueLinkType IS EMPTY I believe that would still include issues with an epic parent but exclude all other link types. Kind regards, Bill

Hi @Scott Schellhardt I believe you may remove that branch on most-recently-created issue, and instead either: * use variables to save the keys as issues are created from {{createdIssue.key}}, and reference them in the epic link and issue linking, or * use the smart value {{createdIssues}} (i.e., note this smart value is…

Hi @Yenni Giang What do you observe happening when the due date is changed? Please post images of: * the rule details at the top of the page, as they will indicate the rule's scope * the audit log details showing the rule execution As this rule is trying to access and update issues in multiple projects, the rule's scope…

Hi @Marius Fischer Looking at the image you posted... The smart value {{createdIssue}} refers to the last issue created during the rule execution: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue-- Please try changing that to just {{issue}} Kind regards, Bill

Hi @sabrina.trono -- Welcome to the Atlassian Community! Where do you have the information for the user who emailed the service desk? If that is stored somewhere in the issue, it may be possible to use an automation rule to parse that out, identify the user, and then set the reporter. If you want to try that approach, here…

Thanks for that information. Are you creating the new sprint from the backlog, or are you creating the sprint from the Complete Sprint dialog and selecting the option "new sprint"? When I tried the second path I was able to cause a near overlap of sprints. There is a related defect in the public backlog where burn charts…

Gotcha, and well done! I have not found in the documentation the defined order of sprint values when issues carryover. Other questions have successfully used last as you are doing, so the only watch item may be edge cases: * remove an issue from an active sprint * added it to another, future sprint * oops...realized that…

Hmmm...that may not always work due to coincidences of other issue creation timing (and Atlassian service outages ;^) I recommend keeping a close watch on that rule. But the way, when I tried adding the Re-fetch after the Field Value Changed trigger for the clone scenario, it worked. So this may still be the first problem…

I recommend writing a rule and experimenting to get the results you want...perhaps only emailing yourself initially until done. Your rule may need to handle two cases, so investigate using the if / else type conditions. For example: * trigger: issue transitioned * if / else condition* condition: issue type is epic *…

Hi @Nikhil Mohanty There is nothing built in for the Jira Cloud, standard license to automatically close / start sprints. It is possible to write an automation rule to do this, calling REST API functions with the Send Web Request action. One challenge will be doing this in the correct step order when you want to do things…

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

Hi @Dez-Luan Unfortunately (in my opinion), there are currently two different story point fields in Jira Cloud: * Story points: used by company-managed projects * Story point estimate: used by team-managed projects The UI is inconsistent in some places, either only referring to "Story points" or explicitly showing the…

Hi @Bhanu Prakash That is possible with a REST API function, and the expand=JQL parameter. Although that would be quite cumbersome to do for 5000+ filters as you would need to page through them. A better approach might be to write code or a script to iterate the pages, or use a marketplace addon. For more information about…

Hi @Ömer DUGAL -- Welcome to the Atlassian Community! There is no built-in behavior to automatically remove issues from a sprint when they are completed. There are features to hide them when enough time has passed (e.g., 2 weeks for a team-managed project board). I suggest reviewing one of the issues, checking the issue…

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

Hi @Maria Christensson and @John Funk That symptom seems related to this one for a C2C migration path: https://jira.atlassian.com/browse/CLOUD-11564 Kind regards, Bill

Hi @Ankit -- Welcome to the Atlassian Community! How are you completing one sprint and starting the next: manually, with your own code calling the REST API functions, with a marketplace addon, etc.? If with your own code (or an addon), perhaps there is a timing problem where the new sprint is started before the previous…

Hi @Michael Besems Teams using Scrum practices often have stable, planned work, with infrequent disruptions for unplanned work. This stability is one of things helping a team develop a predicable velocity for forecasting and a basis for improvements. The steps in Jira to change sprint scope may actually help slow the team…

Hi @Ahmet Fatih Ayyıldız Adding to John's answer, and following up on your note about trying one rule: That may be possible, although it is a bit more complicated. There is a limitation that this can only work for up to 100 issues. If you have more, please use the 2-rule approach John describes. The idea is to gather the…

Hi @Mohit Jain What have you tried thus far to solve this need? If you have started a rule and it is not working as expected, 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…

Please examine the issues involved (the original one and the cloned one moved to the other project) to confirm the links still exist in the issues. For the audit log you show, the issues do not appear to be linked. To confirm your rule scope, please post an image of your rule details at the top. This is the section showing…

Your second question is easy to answer: add the maxResults parameter. yourJiraUrl/rest/api/3/filter/search?expand=JQL&maxResults=100 The more challenging one is paging through blocks of 100 using the startAt parameter. This is typically done with code in an application or script, although you could do it manually. For…