Bill Sheboy Expert

Thanks for clarifying! Smart values are name, spacing, and case-sensitive. And, they often are not exactly the same as the displayed name on the page for the field. When the incorrect smart value is used in a rule, if often fails with no error and instead just returns null. To learn the correct smart value for a field,…

Hi @Scott Franz -- Welcome to the Atlassian Community! I am curious about your scenario: why not just set the story points rather than adding from labels? I find it unlikely this is to implement some type of "voting" or "planning poker", as the label could only have a value once, correct? Until we know that... The format…

Hi @Donna Benton You are trying to do something 3 days after the transition to done, but your trigger is on the transition to done now. That happens at that moment in time. To do what you ask, you could change to use a scheduled trigger (e.g., running once per day), and use JQL to identify any Done issues to move to…

Hi @Steve Suranie Some quick question to help diagnose this... Who is the rule actor for that rule, set in the details at the top of the rule? Is it still the default of Automation for Jira? If that was changed the triggering user may not have access to the field. What type of project is this rule in: company-managed or…

At that point in the rule, "current issue" or {{issue}}, refers to the trigger issue still. If you want to add subtasks to that second, created task, please change your branch to Most recently created issue.

Hi @Chase Ferguson Here are some questions to help diagnose this a bit... Is this happening consistently, for all issues with the markup / formatting? Is everyone on your team seeing this symptom? Is this happening for all projects in your Jira instance? From what you describe, does the formatting change always happen…

Hi @Roger Hall Automation rules trigger after something has happened, like issue create. And so they cannot be used to create a template before that point. For some scenarios, that is not such a problem. For example, some may quickly create an issue, wait for the rule to run, and then immediately edit it to use the…

Hi @Rafael Diaz -- Welcome to the Atlassian Community! Yes, and...to Laurie's answer...One quick way to start is to: * create a saved filter spanning all the relevant team's Scrum boards, * use that to make a shared Kanban board, stored in one of the projects (or another project), and * remember to treat that Kanban board…

Thanks, Mark. Just to confirm what happened: using the smart value "Story point estimate" from lookup issues did not work, but the custom field id for it did work?

When setting the Epic Link in the issue create, you cannot copy from trigger issue because it is an epic (and has no parent epic). My apologies if I was unclear! Instead type in the smart value {{triggerIssue.key}} and it will appear below the field. When it does, select it to use it.

Let's confirm some terminology first...The out-of-the-box issue hierarchy is: * Epic* Story, Task, or Bug* Sub-task And so when using the related-issues condition to check for Sub-tasks, it will never find them as the trigger issue is an Epic. After that condition, the rule adds what appear to be new issues at the Task…

Looking at the rule you have posted, are you trying to make the newly created Task a child issue of the trigger issue, epic? If so, have you tried to set the epic link at the same time as the issue create? Please show an image of that rule action.

Thanks for clarifying. If your issues are all assigned to a fixVersion you could find them with JQL, using those functions. For example, https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#earliestUnreleasedVersion-- And then use the lookup issues action to gather them for…

When I just tested this, here is what I observe, as expected... * when: create a new story* a rule with an issue created trigger runs * a rule with an issue updated trigger does not run * when: move the story to change the type to epic* a rule with an issue created trigger does not run * a rule with an issue updated…

Would you please post an image of that issue, NSDAT-12423, including the complete issue history information? When I just tried an issue type change, from story to epic, for a company-managed project, it shows as an edit, and not as a new create.

Hi, Sarah. Do you have a production support team who would know the admin for your Jira instance? If not... @Valerie Knapp as you are in a Community Leader role, would you please ping the Atlassian team to have them get in touch with Sarah to help? Thanks!

Please re-read what I posted above, including... Rules get issues from the trigger, actions, and conditions. Your rule has no trigger yet, so you would need to select one for the community to know how to help with your rule. Rules can process, at most, 100 issues. Does your project have more than 100 issues? If your rule…

Hi @Devon Chan 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 @Derrick Lim -- Welcome to the Atlassian Community! My understanding is the Issue Moved trigger for automation rules only fires when an issue changes projects, and so that will not help for your scenario. Next, the Issue Created trigger can fire so quickly that the data is not yet available for the rule to use. I…

Thanks for that information. I wondered if you had a marketplace addon which might be influencing the behavior of the validators. I took a quick look in the public backlog and did not see this symptom for any defects. Was the subtask transitioned to done on the parent issue view (that is, while the view was showing)? In…

The {{fieldChange.toString}} smart value will just be text, and not a list of values. Your two options are to use the split() function on any commas or to specifically use one of these smart values: {{addedFieldChange.valueIds}} or {{addedFieldChange.values}}…

Thanks for that information. Here are 3 specific steps for you to try. Please perform them in the order shown. * Review the introductory documentation on automation rules. That will help you understand how rules are written and work. https://www.atlassian.com/software/jira/guides/automation/overview#board-vs-project *…

Hi @Julia Müller What problem are you trying to solve by doing that? Knowing the "why" will help the community to provide better suggestions. Thanks! Until we see that... Most of what you describe could be done with a JQL filter to identify the issues. And that JQL could be used with a scheduled trigger, automation rule.…

Would you please post an image showing the audit log details (under "Show more") for the rule execution? That may help to explain what you are seeing. Is the newly created epic in the same Jira project as the one that triggered the rule, or a different project? If so, is your rule a project-scope or global / multiple…

Hi @Dd There are at least two ways to check the content of a field to perform the behavior you ask: Use text and conditional functions to extract / test the value, and then add your field. Please look here to learn about those: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/…

A scheduled trigger can only use valid JQL, and that is not valid JQL. Let's return to the earlier question, as I am not explaining this well and your rule is not valid. What is your Jira version: Cloud, Server, or Data Center? After you have answered that question we can continue. If you do not know the answer, please…

Please show the details of your scheduled trigger, including the JQL you are using. In your email body, you are using the lookup issues smart value. But first you must use the lookup issues action or that smart value will not work. * If you review the documentation for that action, it shows how to use the smart value with…

Your rule does not have any issues provided and so the email is empty. To help solve this, what version of Jira are you using: Cloud, Server, or Data Center? If you are using Jira Cloud or Data Center, you may use the lookup issues action with a JQL statement to return the issues. Please look here to learn more about using…

Please select "Show more" to see the details of the rule execution. Repeating my earlier question: what is the JQL you are using for your scheduled trigger? And have you tested the JQL outside of the rule to confirm it works as expected?

Hi @Peter Ruan -- Welcome to the Atlassian Community! One way to do that in an automation rule is: * write a JQL statement to find the issue (e.g., where the parent equals the epic's key and the summary contains what you want to check) * use that JQL with a lookup issues action * check if the result count is 0 (i.e.,…