Bill Sheboy Expert

Hi @David Ashlock Yup, and I believe you just have a couple of smart value capitalization and spacing issues...this worked for me: {{lookupIssues.duedate.max.diff(issue.Start date).businessDays}} Kind regards, Bill

Yes, indeed. Those fields did not exist in Lookup Issues when this question was first posted, so the solution is now easier to implement.

Correct; that is why I suggested replacing your second JQL condition with a Lookup Issues action with JQL to check for any sibling issues (same parent) and which are not done/completed. Then use an advanced compare condition and only proceed if the following value is zero: {{lookupIssues.size}0}}

Hi @Viktoria Neudecker -- Welcome to the Atlassian Community! This is possible to detect, and you may want to consider more criteria or the rule could return a lot of issues. An example rule to do this, with a built-in stopping condition would be: * trigger: scheduled with JQL for the issues you want to check. For example:…

Hi @JD Lobue Yes, and...to what @Sachin Dhamale suggests: You may also add a simple automation rule to the project such that when an epic transitions to a completed status, the "Epic Status" is also set to done...automagically removing it from the epic panel and dropdown lists. Kind regards, Bill

Hi @Victor Cordeiro Costa Jira Cloud automation rules can be project-scope or global/multi-project scope. To do what you ask your rule would need to be defined as global/multi-project scope. To make that change, please talk to your site admin to modify the rule. And please note: the different Jira license levels have…

Hi @HimanshU PrasaD -- Welcome to the Atlassian Community! Jira has no built-in features for planning poker, so your team is using some form of addon product from the marketplace for this feature. Please talk to your company's Jira Admin to identify the vendor and then contact their support team via the marketplace, or…

Did you update the JQL as noted earlier as that image still appears to be missing the double-curly brackets around the smart value? "Customer Ticket" ~ "{{triggerIssue.Customer Ticket}}"

I believe the default email handler puts the information in the email body into {{issue.description}} so you may use that with the action to comment on an issue in the rule.

Ah...that second thing is the Jira/Excel date format mismatch. Perhaps try this to solve both issues at once: Create Excel named variables which point to your cells, and in the named variable use Excel's TEXT() function to convert to data format Jira is wanting and forcing to "text" in one step. Then reference the named…

It appears you only have a single rather than double-curly brackets for you smart value in the JQL. Try adding that to see how it helps.

Hi, Chris! It appears you want to identify: people who have nothing in-progress AND who have non-done work assigned to them. Is that correct? If so, how often do you need to perform this check, and what will you do with the results? * Need this often to provide reporting: investigate marketplace addons for JQL to perform…

Hi @aagrawal What do you want in your release notes information? If you want something with lots of formatting/markup, you may want to investigate the marketplace and purchase an addon. If an email (or Slack/Teams message) would be sufficient to list the released issues, consider writing an automation rule to send this…

Hmmm...if that branch type does not work due to the linking, please try a branch on JQL to get at the parent. You can test that JQL first with advanced search and once you have what you want, use it in the branch. And...you do not show the details of your second "JQL issues match" condition to check for remaining items as…

Hi @Scott Federman Would you please post an image of the audit log details, showing what happens when the rule executes? That may help explain what is happening. Thanks! Kind regards, Bill

No, I have only done it as mentioned in that other post or with saved filters. What happens if your remove both the quotation marks and ampersands: will the plugin resolve it then? status CHANGED TO "Dev Complete" DURING ( Weeks!$B$6, Weeks!$C$6 )

Hi @Iain McCarthy I do not believe there is anything built into Jira Cloud to do that. A couple of work-around options are to: * investigate the marketplace for addon apps for purchase to help manage filters * call the REST API functions to figure this…

Hi @Chris Luck -- Welcome to the Atlassian Community! That is an interesting use case... To save you some time, my experiments with smart value list filtering show that other lists cannot be used inside the iterator for filtering...and neither can created variables (as a work-around to the first problem). My suggestion is…

Hi @Tom Gagne Please take a look at the examples in this question's solutions, as I believe you are missing some ampersands to make the query concatenate correctly and use of nested quotation marks:…

Hi, Sabrina. Based on your description please consider the following: * What you describe seems like you are re-implementing service desk functions using email and newly created Jira issues. Please consider investigating if Jira Service Manager would be a better approach. * Rather than relying on the summary, I recommend…

Hi @Sten Kivi -- Welcome to the Atlassian Community! When you noted: Problem is that if user only has ,,Access on site" permission my automation works but if i add on top of that ,,Jira Software" my automation gets errors Are you changing the user (actor) for the automation rule, or are you changing the permissions for the…

Hi @Saranya A -- Welcome to the Atlassian Community! By "capacity planning" do you mean: * when the team is all present for work for the entire planned sprint, our capacity is fully available (e.g. 100%) * when one or more people are out of office (e.g. vacation, holidays, training, etc.) our capacity is reduced * using…

Thanks for that information. For your use case of wanting to link issues, the Lookup Issues is probably not what you need. Instead you probably want to branch with JQL to match the issues for the linking. Before changing your rule further, would you please clarify what is creating the issues that is triggering this rule:…

Hi @Mathilde Courtat Let's try creating a new very simple rule to learn what is happening. * trigger: manual * action: log to the audit log the value {{issue.Zendesk Ticket Count}} Then find an issue you expect to have a count and run the rule from the issue (under the lightning bolt icon). When you check the log, what…

Thanks for that information. When you look at the specific epic's history/activity what does it indicate is changing the date back?

Hi @Andrew Grossman JQL is not a SQL, and so does not support the nested/correlated query syntax needed to do what you ask. Some options to help your use case are: * buy: investigate marketplace addons for purchase that enhance JQL * replicate data: use automation rules based upon changes to the epics to somehow mark the…

Hi @Michael Cheng Yes, and to what Jack suggests: If this is for JSM, please check {{issue.comment.internal}} as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--comment-- Kind regards, Bill

Hi @Louis Andrews As you are noticing for your {{issue.customfield_11102}} information, not all of the other fields are present. If they were, Jira would potentially need to load every single possible issue in a tree of issues when the rule executes. Your alternative is to use a branch or Lookup Issues with JQL to get at…

Hi @Wensi Song Would you please clarify what is happening? That may help explain what you are observing. For example: * From where are you changing the epic's start date: edit view, on the roadmap by dragging the handles, etc.? * When you look at the history information for the epic, what does it indicate is happening? Who…

Hi @Alison O'Donnell Yes, and...to what Nic and Joe noted: What you can do to solve this is use the {{createdIssues}} smart value in your automation rule which creates the issues to get the keys. For example: Here are the created issues' keys: {{#createdIssues}}{{key}}{{^last}}, {{/}}{{/}} Please look here for more…