Bill Sheboy Expert

Consider adding a split(" ") before the match to improve the chances of a match when there are newlines and other formatting in the comment. They try re-testing. If that does not help, please post an image of the updated rule and the audit log details from the rule execution.

Please post images of your current complete rule and the audit log details showing the rule execution. Thanks!

Hi @Martina There are a few things to check / adjust in your rule: What is the field type for "Install_Date"? Is it a date picker field, or something else? Have you confirmed that is the correct smart value for the field, Install_Date? Smart values are name, spacing, and case-sensitive. And often the smart value does not…

Hi @Kylie Alvarez How are you representing definitions of done (DoD) today in the issues? Knowing this will help the community to offer better suggestions. For example, are you using a checklist field (or addon) for the team to mark things off? Or perhaps just pasting in the list of items as text in a field? Until we know…

Hi @Regina Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions. Thanks!

Hi @Antony Smith Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions. Thanks!

Hi @Jeremy Derbord Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not... With the Sprint started trigger, that should be a single sprint value, not a list of values. And so the smart values for your email would be: {{sprint.name}}…

Hi @conrad_w -- Welcome to the Atlassian Community Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions. Thanks, and kind regards, Bill

Hi @Rolo Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions. Thanks, and kind regards, Bill

Hi @cho Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks!

Hi @Cash Coyne Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks!

Hi @Gil Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks, and kind regards, Bill

Hi @Yael Bichovsky Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks, and kind regards, Bill

Hi @Steven Theodoor Bosman-Romein Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks!

Hi @Blacke조민기 Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community provide suggestions. Thanks!

Because you have two different rules, with the same trigger and no conditions on issue type, they are eventually colliding. Regarding that Resolution error, I recommend checking the workflow for any sets of resolution. Back to your original question: if you want two rules, I recommend adding a condition immediately after…

I'm glad to help! You may want to also take a look at this overview documentation and example rules in the library to see other techniques...and review the smart value list to learn what is available: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

Hi @Jimmy Yu -- Welcome to the Atlassian Community! That depends upon how your rules are written... 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. Those will provide…

By default, I believe they are linked with the "clones" link type. If you want a different link type, the link can be added after the issue is created in the rule: * When the issues are in the same project, you can either branch to the most recently created issue to link to the trigger issue, or link from the trigger issue…

Hi @Nate Dickinson Please try using the statusCategory for the issues instead: statusCategory = Done Also please note, if you are using any Scrum boards: the statusCategory is not used to determine if an issue is completed for a sprint. Instead it checks for issues in a status mapped to the column at the right side of the…

Hi @Cash Coyne My understanding is this is a known problem if there are (or have been) team-managed projects used in the site with a status of the same name. The work-around noted in a few open defects is to use the status value's id rather than its name. https://jira.atlassian.com/browse/JRACLOUD-70797…

Hi @Mandy Trickey Please note the Epic Name and Epic Link field are essentially sunset now in Jira. The Summary and Parent fields are used instead. I recommend updating your JQL for the lookup issues action inside of the branch to use parent = {{issue.key}} rather than "Epic Link" = "{{issue.Epic Name}}" Kind regards, Bill

I am glad to learn that helped, and... Regarding removing "CLONE" from the beginning of the Summary field text, when you use the Clone Issue action it allows you to update the fields, and the Summary field shows by default with this: CLONE - {{issue.summary}} You can change that in the action to not add the prefix text:…

Hi @Richard A_ Michaels 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…

Hi @Mirko Grahnert Yes, and...to Sam's suggestion: The key for your scenario and changing / setting the parent of those issues is rule scope. You describe the implementation issues in another project (outside of JPD), and so the rule will need to be at the global level and have a scope of "global" or "multiple projects" to…

Hi @Till What problem are you trying to solve? That is, why do this? Knowing that will help the community to offer better suggestions. Until we know that... Are these new issues added to the sprint which just started, and so already linked to it? If not, what is the purpose of these newly created issues relative to the…

Hi @Avinash Bhagawati _Appfire_ As a reminder...When recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Deev Sethiya This appears to be due to having subtasks with the issues, and those subtasks do not have due date values: only their parent issue has them. And the parent is only shown as a heading for each section of subtasks. Do any of your subtasks have due date values which are not displaying in the backlog or on the…

Hi @Adriana Marquez I respectfully suggest you are trying to fix a process / team behavior problem with an automation rule. Instead consider: why are team members trying to move multiple issues into in-progress, when the team apparently has a working agreement / policy to only work on one item at a time? Understanding the…

Hi @Yenni Giang -- 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…