Bill Sheboy Expert

Hi @Daniela Cardenas Are you asking a question regarding how to build such a rule, suggesting this as a new Jira feature, or something else? If you are asking about creating a rule... You describe when a sprint closes to then create two more sprints with a specific naming convention. * Would you want your rule to…

Hi Bryan, Looking at the image of the rule you posted in the question, I wonder if it works as you expected regarding created variables: are you expecting that created variable to be updated and usable after the branch? If so, please note... * Branches on one-and-only-one-thing (e.g., branch on current issue, parent, etc.)…

Hi @Younes Abou Khzam -- Welcome to the Atlassian Community! That smart value you are using appears incorrect. User fields (such as reporter) have an attribute named accountId, and so to reference it you would use {{issue.reporter.accountId}} Please post images of your entire rule and the audit log details showing the rule…

Nope: my understanding is there are no built-in fields for cycle times, lead time, and other such process flow measurements (e.g., WIP, age of WIP, etc.). Instead there is a built-in, interpretation of a control chart for boards to show such measures. But those are only viewable by looking at the report and hovering over…

I wonder if this is a side-effect of the changes around allowing re-using of fields in team-managed projects. Let's absolutely confirm you have the correct custom field id for your specific project: * identify an example issue with your field * use this how-to article to identify the smart value and custom field id for…

Hi, Dave -- Welcome to the Atlassian Community! Those are not built-in fields, and are likely custom fields added by your Jira admin(s) or by a marketplace addon app. So first thing, I would identify the purpose of those fields. If they were added by a Jira admin, you may need to either manually clear them or use an…

Hi @Jordan_Jones -- Welcome to the Atlassian Community! There are problems with some of the team-managed project fields not working in emails (e.g., People fields). Although I just tried a test rule and the paragraph fields worked for me. Would you please post images of your complete rule and the audit log details showing…

Hi @Rebecca Hylek There is a new, recent defect for that here: https://jira.atlassian.com/browse/AUTO-804 You can watch / vote for it to see progress. Kind regards, Bill

Hi @Mazen ElAasser Based upon the complexity of your calculation, you may be able to use the built-in custom formulas feature of Jira Product Discovery: https://support.atlassian.com/jira-product-discovery/docs/expression-based-formulas/ If that will not handle your use case, you could perform more complex calculations…

That sounds like a defect to me...I am not using Jira Server / Data Center and so I can experiment with what you are observing. When you note you cannot filter by End Date, is End Date a field you added? Normally the two built-in fields are Start Data and Due Date for planning ranges. Can you send people the filter rather…

Hi @Keshav First thing, this may be a learning opportunity for the team, helping them understand the board is a tool to help them manage work. And so moving items as they are worked upon helps everyone. Back to your question: I recommend a simpler approach to focus on what is happening now. For example, if an issue is…

Well done! And an FYI... When using branches in automation rules, scope is important...particularly with issues and created variables. Specifically: branches on one-and-only-one issue get run in-line (e.g., branch on current issue, branch on parent, etc.), as if the branch was not there. All other branches run in-parallel…

Interesting...do you mean on the issue on the board, in the backlog, or somewhere else? I know that not everything in Jira automagically refreshes on the page/view when changes are made. When you do a page refresh does the field value appear?

I am glad to learn that helped! Regarding the End Date field, is it added to the issue view? If so, you may want to check with your Jira admin to learn why it is not visible.

Hi @David Gauthier What problem are you trying to solve by doing this? Knowing that may help the community to offer other suggestions. Thanks! Until we know that...and until we see your complete automation rule details... Perhaps try this to return issues which have at least have component B: project = yourProjectName AND…

Hi @Simmo After retesting this morning I was not able to repro the symptom I saw where a number stored as a created variable could not successfully look up a table value with get(). I sent you my rule in a separate communication. I will update my earlier post accordingly.

Is your custom field a user field or something else? If it is a user field the accountId value is still available: {{issue.myCustomUserField.accountId}}

Hi @Melody KirkWagner Smart values are name, spacing, and case-sensitive. I believe the smart value for the Start Date field is "Start date", so please try this: {{issue.Start date.plusBusinessDays(140)}} You can confirm the smart value for a field using this how-to article. Essentially you identify an issue with your…

Hi @Breanna Williams Would you please post images of your complete rule and the audit log details showing the execution? Those may provide context for the community to offer ideas. Thanks! Until we see those... I am unclear why you would need an advanced branch for this scenario. An alternative would be: * trigger: issue…

Thanks for that information, Stephanie. I recommend taking a look at the documentation page for the Xray addon. That will probably show examples of using automation rules with their tool.

Hi @Maximiliano Vai -- Welcome to the Atlassian Community! No, that is not possible with out-of-the-box features. Your work-arounds depend upon how often you need this type of search and you willingness to purchase addons/build things: * need this one time* export your issues to a spreadsheet (or another tool) and perform…

Hi @Stephanie Hansen How are you implementing tests in your project: with a marketplace addon or with Jira issues your team added? Are you using Jira Cloud, or the Server / Data Center version? What have you tried thus far to solve this need? For example, if you have started an automation rule, please post images of your…

Hi @anthony.madrigal -- Welcome to the Atlassian Community! That appears to be a known defect, and you can watch / vote for it to follow here: https://jira.atlassian.com/browse/AUTO-804 Kind regards, Bill

Thanks, @Gergana.Damyanova And an FYI for @Simmo -- It seems there is a difference in behavior when using a Created Variable as a value for the get() in lookup tables: * when the table key and variable represent a value that cannot be interpreted as a number (e.g., "Five") the lookup works * when the key can be interpreted…

Hi @Mykhailo Shukakidze I believe you need to use the id value rather than the name. Have you instead tried the "Copy from parent" option from the ... menu at the right of the field? Kind regards, Bill

Hi @Deepak Prasanth Have you tried adding a delimited list of the accountId values for the users to the table rows? Once a row is selected, it could be split by your delimiter for use.

Hi @Gergana.Damyanova For what you are trying to use a created variable as the get() parameter, the syntax would be: "customfield_10464":{"value":"{{otherteams.get(linkedIssueKey)}}"} However I retested and that seems to also not work.

Thanks for that information, Gabriel. The epic link field is not relevant for the subtasks. I can understand that logically for the hierarchy it may make sense: subtasks are part of a story, the story is part of an epic, and so the subtasks are part of the epic. But practically they are not as subtasks are only part of…

For the JQL in the Lookup Issues action, please try something like this: project = insertYourProjectName AND fixVersion = {{version.name}} Regarding the error you are seeing, please note I suggested using the Lookup Issues action, and so you use the {{lookupIssues}} smart value and not {{issue}} When you needed the…

Hi @Leena Pratheepan Please try using the Lookup Issues action instead of a branch: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues You could use JQL to find the issues in the updated version, and then send a single email listing all of them: * trigger: version updated: * action:…