Bill Sheboy Expert

Hi @Geethanjali S J Yes, and...to what Mark suggests: I would change the condition from "Issue type not equal to Epic" to be "Issue type is one of the following..." using the types you use under epics. That may prevent any side-effects for parent/child changes later by the automation team (e.g. team-managed projects). Kind…

I am using Jira Cloud, and all of those worked for me in a test rule. Perhaps this is something different about the smart values for Jira Server/Data Center. I suggest working with your site admin to submit a ticket to Atlassian Support to see what they can find: https://support.atlassian.com/contact/#/

Hi @federica.niero I have observed that sometimes rules get "glitched" in Jira Cloud after too many edits, particularly to triggers and the sub-settings in actions. Please keep this rule disabled, and then try to re-create it from scratch to see if it works as expected. By the way, I asked if this is a company-managed or…

Would you please post images of: * the details of your send email action * the details of the audit log showing the error after you made the changes to the rule That may indicate what is happening. The other possibility with Jira Cloud automation rules is they sometimes get "glitched" by changing the components to many…

I just reproduced that symptom on a test dashboard and the total time is now blank/empty even though the issues have estimates. Seems like a defect and I recommend working with your site admin to submit this one to Atlassian Support: https://support.atlassian.com/contact/#/

Hi @Harmeet Singh You do not show your entire automation rule, and I wonder if there is a context problem where the email is seeing another issue. Perhaps add the missing prefix for issue. such as: {{#if(issue.components.isEmpty)}} * The epic does not have any components assigned. Component is empty {{/}} If that does not…

Hi, Jean! Did you change the field used for the gadget? If so, that would seem to indicate the gadget does not recognize it as numeric any longer.

In that expression, you appear to be trying to changing assignee twice: once in the "update" and once in the "fields". And, you have a "set" prior to "fields", but "fields" is a shortcut to using "update" and…

Hi @Fiorella Santopietro You cannot do that with the user's name, and instead need to find their account id, as shown in this example: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Using-smart-values If this is always for the same specific user you may find their account id with a…

Hi @IT If you want to run this query for a single, specific day, the built in advanced JQL functions would help you create a saved filter...and you could then schedule that to notify you. If instead you want to run this for all existing and future issues, that is not possible with out-of-the-box JQL features. You would…

Hi @Evan Nixon There are a few things to address in your rule to help: * You only wanted one new issue per month (correct?), but your scheduled trigger uses JQL and so that will run for each issue found. Instead please remove the JQL from the trigger. * Lookup Issues' smart values only have information when you first use…

Once you removed the JQL from the scheduled trigger, the Send Email now needed another source for that issue information: Lookup Issues. Please try using {{lookupIssues.size}}

Hi @Nicolas Zuderell -- Welcome to the Atlassian Community! For a question like this, please post images of your complete automation rule and of the audit log details showing the run of the rule which does not work as expected. That will provide context for the community to offer suggestions. Thanks! Until we see that…

Hi @Sanjay Mukherjee As your test management tool is a marketplace addon, I suspect that field is a custom field from the vendor, and it is calculated just-in-time for display dynamically in that page view. Perhaps contact the vendor to learn if there are dashboard gadgets they know support this field. Kind regards, Bill

Hi @Clarisse -- Welcome to the Atlassian Community! Although team-managed projects do not have card color/layout configuration yet, you can use "custom filters" to narrow what is displayed for the labels. This feature works similar to Quick Filters in company-managed projects. Please review this documentation article to…

Hi @Kevin hankinson In my opinion, "yes it is doable and yes it makes sense". Showing the complete value stream at this scale could help with demand/capacity/readiness conversations. For example... What if your "business level" board kept the work items on it rather than moving them and instead the automation cloned them…

I am glad to learn that helped! By the way, when you are trying to find the correct smart values to use for a field, this how-to article can help. Basically you find an example issue and call the REST API from a browser tab to list all possible smart values.…

Pondering this a bit more, it would be possible to make this adjustment to assignment auto-magic by either: * Create a separate group which you update, and it only includes the people currently available for assignment. Then update the rule to use that group. * Create a separate group for people who are…

Hi @Jasmin Rizko Are you performing the assignment with an automation rule's Assign action? If so, it appears round-robin uses the sequence of users in the list/group and thus would select User 2 in your example. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue Kind regards, Bill

Hi @Kazumi Kerr You cannot perform such a query with out-of-the-box Jira JQL features. Specifically, you are trying to check fields of the epic and excluding epics from the query. Such queries require correlating different query expressions to join the epic and non-epic information. If you need this type of query…

Hi @Stijn Coppens The details of your use case are a bit unclear to me. It seems you want to set the issue's Priority field based upon some criteria when the issue is created, or added to a sprint which is not in progress. Is that correct? If so, you could do this with a couple of different automation rules. For example…

Hi @John DiNatale -- Welcome to the Atlassian Community! For JQL wildcard searches, use an asterisk to find matching text in whole "words"...and...that wildcard cannot occur at the start of the search string. For your example, this could not work: project = RPD AND summary ~ "*V01.01.00.0237" But if you knew the prefix was…

Hi @Noelia Belen Lopez -- Welcome to the Atlassian Community! Were you able to see them before the edits? According to this suggestion the dashboard feature is not supported on the mobile app yet: https://jira.atlassian.com/browse/JRACLOUD-63281 Have you tried to open the same dashboard in a browser on the device? Kind…

Hi @federica.niero Is this rule running in a Company-managed or a Team-managed project? Would you please post an image of the audit log showing the details for when the rules but does not copy as you expected? Kind regards, Bill

Hi, Jim. Please take a look at the more advanced solution I noted earlier, where you use a custom field to track status changes with one rule and then use that value in your current one instead of Updated. And if your workflow is very simple, such as ToDo, InProgress, and Done...there is a built-in field which can be used…

Hi @corinne.sabom From what you are describing, your Epics contain multiple child items and those child items are being released to production over multiple Jira Versions (releases). If that is correct, I believe you are correct that it would be better to remove the Epics from the release and to only track the child items.…

Hi @Peter Jeffery You cannot add numbers like that in a smart value expression without using the mathematical expression syntax: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Instead, please try using the plus() function, such as:…

Hi @Fabio Racobaldo _Catworkx_ Minor typo as I believe it is membersOf() https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-membersOfmembersOf-- Kind regards, Bill

Hi @tasha tokunova When your rule is inside of the {{lookupIssues}} you no longer use the {{issues...}} prefix to the smart values. Their context is the lookup, and {{issues...}} refers to other contexts, such as either the trigger issue or issues within a branch. Please try this: inside of the lookup iterator…

Hi @David Loszewski For your first question, please take a look at the available formats for smart value date/times to pick the one you want: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ For your averaging question, the answer depends upon how many issues you want to average for this…