Bill Sheboy Expert

Hi @Ryan Johnson D Ultimately this can be improved with communication to stakeholders, and transparently explaining what the team is doing and why. To answer your second question first, the built-in charts have little configuration for mixed things like sizing with story points and an odd time-based item in the same…

You do that with the and() expression, like this: {{#issue.subtasks}} {{#if(and(status.id.eq(10001),assignee.displayName.eq("1234")))}}{{key}} {{status}}{{/}} {{/}} https://confluence.atlassian.com/automation/jira-smart-values-conditional-logic-1081351607.html The logical and() and or() functions only accept two…

Interesting that the filter worked, although that is good news! Let's try your code with a more specific condition on the id for the status...rather than letting it assume the default attribute: {{#issue.subtasks}} {{#if(status.id.eq(10001))}}{{key}} {{status}}{{/}} {{/}}

This seems to indicate the smart value expression is the cause. Let's try to write just the field to the audit log: {{issue.customfield_19022}} That will confirm if it contains what you expect before using the diff() function on it.

Hi @Andrew Stolcers -- Welcome to the Atlassian Community! I do not believe that smart value, list filtering works with the Server/Data Center version of automation yet. The only work-around I can think of would be to use JQL for your conditions with a branch, enabling the bulk-handling feature, and then use the {{issues}}…

Hi @ting sun -- Welcome to the Atlassian Community! A Jira board is a view of issues, based on the board's filter. And so it is likely that when you create the new issues they are not meeting the filter criteria, and so do not display. For example, are you creating issues missing a piece of information, or perhaps in one…

Thanks, and unfortunately some of the errors automation rules show are not clear on what is happening... I wonder if this has something to do with whatever the name is of the field which you are concealing, perhaps due to some embedded, or reserved, character. This could also be due to an issue type name containing…

Hi @Bruno Mello -- Welcome to the Atlassian Community! Yes, that is possible, and there are several examples of this in community posts, and similar rules in the library for projects. I recommend triggering the rule on several scenarios to help with accuracy: * when an issue is created * when an issue's time estimate is…

Hi @S Would you please post images of the actual audit log details for the rule execution and of the details of your branch action? Those may provide context for this symptom. And also...smart values are name, spacing, and case-sensitive. The one for the trigger issue is this: {{triggerIssue}} Kind regards, Bill

Hi @Brian Lehmbeck A query like this is not possible with the out-of-the-box JQL features. How often do you need to do a query like this, and how many issues do you think meet this criteria? * need just one time* You could search for issues which contain that starting text, and then export the issues to refine the search…

There appears to be something different with your rule, or with Jira Data Center, in this automation scenario. Let's try this step by step... Please replace your edit with a write to the audit log for just the remove expression value: REMOVE: {{#changelog.labels}}{{#fromString.split(" ")}}{ "remove": "{{.}}" } {{^last}},…

Hi @[deleted] The pound # symbol is one of the reserved characters for JQL, and according to this defect the documented way to search for such characters does not work: https://jira.atlassian.com/browse/JRACLOUD-75866 A work-around could be to trigger on all comment changes, and then try either an advanced compare…

Yes, like that. Also try writing just {{issue.customfield_19022}} to the log. Then run your rule and post an image of the audit log details. Thanks!

Hi @Jordan Wilkinson I believe that would be the last sprint added to the field, and not necessarily the last sprint relative to the name, start/end date, etc. Kind regards, Bill

If you write the custom field and the expression to calculate the date difference directly to the audit log in the rule, what do you see?

Thanks for clarifying, Karen. What I think is happening is created variables are always text type (at this time...) and so your variable needs to be converted to a number for the format() function to work. (Format can also work with date/time types...which are really number behind the scenes.) Please try this:…

Hi @Karen Kelly Are you trying to change the stored value in the Total field or the output in some message, email, etc.? If you are trying to change the stored value of Total, what you describe will only work if you have a text field. If it is numeric, Jira will most likely truncate any trailing, zero digits. Or...is this…

Hi @Cristina Carrillo Would you please post images of the details of your issue edit action and of the audit log details for the rule? Those may help explain what you are observing. Also, what do you see if you write that value to the audit log directly with the log action? Kind regards, Bill 

Hi @Conrad Goodman First thing, and IMHO, there are no best practices...only better and worse ones for your team. That being noted, if your team finds it helpful to create the versions with some form of the date included, you can do that using the Create Version action and the date time functions of rules, particularly the…

Hi @James Duffy Yes, and you can use the toDate conversion on the field, such as: {{issue.myField.toDate}} Try using the jiraDateTime or jqlDateTime formats, as defined in the documentation. When needed, also convert to your time zone to enforce the desired value. Kind regards, Bill

Hi @Louise Woods Adding to Trudy's ideas... Are you using a Company-managed (CMP) or a Team-managed project (TMP)? You may find this information at the bottom-left side of the expand area on the browser page. I ask because TMP have always used "parent" for epic linking, and CMP are in transition from "epic link" to…

Hi @tom_thain Creating the automation would be simple...the question is will it work: there are (unfortunately) several things called "Team" in Jira Cloud, and I recall they are not all supported by rules. First thing, I recommend finding an example issue with your Team field set, and then use this how-to article to learn…

I believe that field is a Version name filter, and so you only put in your expression and not the rest of the smart value for the field.

Hi @Tanguy Crusson Let me try a different way to explain the concern... * Jira site admins and org admins can add, enable/disable user access for products, such as JPD. This is the normal method to manage product access, and thus licensing costs. * Jira project admins can administer project settings, such as field/feature…

Hi @Виталий Федякин -- Welcome to the Atlassian Community! What have you done thus far to solve this need? If you have a rule, please post images of the rule and audit log details, describing what is not working as you expect. That will give the community context to try to help. If you have not started a rule yet, please…

Hi @Janek Looschen If I understand your use case, I wonder if there are timing issues in the solution... You stated that: Whenever a comment is written in a Sales Order Service Ticket, that has been created automatically the Jira Automation states to following Audit Log ( No actions performed) * Are the two issues created…

Hi @Renee Troiani -- Welcome to the Atlassian Community! First thing, are you using Jira Cloud or Server/Data Center? And if using Server/Data Center, which version of automation do you have: pro or lite? Knowing these things will help the community to offer suggestions that can work with your version of automation rules.…

Hi @Asadullah Asalm What have you tried thus far to solve this? For example, if you have an automation rule please post images of the complete rule (showing your condition) and the audit log details showing the rule execution. Those will provide context for the community to make suggestions. If you do not have a rule yet,…

Hi @Alex Eldridge How often do you need to do this? If you need this often, I recommend looking at the Atlassian Marketplace for dashboard gadgets/reporting which do this better than Atlassian's interpretation of a control chart. Although some of these addons are not very open about their interpretation of data and their…

Hi @Aditya Rajaraman You note using manual trigger (which is for one issue) and then mention "for every ticket in a given list". How are you determining and accessing that list of issues? While you are answering that question... You can use smart value list filtering and/or the match function to find comment body fields…