Bill Sheboy Expert

Hi @Ramon Masachs -- Welcome to the Atlassian Community! Adding to Trudy's ideas... Using an automation for this scenario will reverse the transition, but it may not solve the root cause of the symptom of moving more into that status than to which the team agreed. Instead that automation could lead to unintended…

Hi @Marc Tseu Weird errors / unexpected behaviors can happen with the Issue Created trigger because it can fire so quickly the issue may not have all of its data when the rule starts. (i.e., a racetrack error) The fix for that symptom is to always add the Re-fetch Issue action immediately after the Issue Created trigger.…

As you certain that is the log for the rule shown as the steps do not match? For example, the log shows a write to the audit log but that action is not in the rule shown. The Issue Created trigger can fire so quickly that the issue data may not yet be available to the rule, causing errors and weird symptoms. I recommend…

Awesome; I am glad to learn the community was able to help!

Hi @Matthew Ogrady Please try the approach @Darryl Lee and I suggested with this answer above to uncheck all of the actions / tasks on the page. The other answer thread is just exploring another approach which may not work, possibly due to some recent automation changes to webhooks. Please let us know how this one works…

That sounds like a different problem perhaps... For about 2 weeks, I have noted latency on the site for the automation rule editor updates on publish, audit log refresh, and even the execution of rules (on a free license). I even noted a new behavior: rules can now spontaneously halt executing, showing the "abort" message…

Your sprint names contain spaces, and as the audit log shows that breaks the JQL comparisons. When using the variable to compare, it must be enclosed in quotation marks: AND sprint = "{{NewSprintName}}"

There was a Jira Cloud suggestion that included nested branching, which is marked as "fixed", but the branch-nesting was not added: https://jira.atlassian.com/browse/AUTO-67 Instead, only some conditional-if nesting was added, and in my opinion, that feature is neither reliable nor easily maintainable in rules. I recommend…

You have been busy trying this one! ;^) I have not used this recursive technique in over two years (and I am not currently in a "production position" whereby to check the rule I did use). When that update about webhooks came out, I recall I carefully read it to check for this scenario. My take: someone will need to contact…

Hi @Christopher Kim For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, * an image of the audit log details showing the rule execution, and…

Hi @Thies Uhlenbruch You could try using a Issue Transitioned trigger to "done", and then use Related Issues conditions to check if the parent Epic, and sibling Tasks, meet the conditions you need to perform the next steps. I recommend trying to write your rule, testing it, and if you run into challenges, post images of…

Hi @Maurice B. Short answer: a single rule cannot send one email for this scenario unless there is fixed / known number of epics (e.g., exactly 10 epics) AND the total number of epics and child issues is less than 100. The reasons are due to rule limits and how branches execute in parallel. If the above criteria apply, the…

Hi @guanjie.ren -- Welcome to the Atlassian Community! That is not one of the built-in dashboard gadgets. That is either from a marketplace vendor or was written by a developer in you company. If it is from a marketplace vendor, please work with your Jira Site Admin to identify the vendor and then check their documentation…

Hi @marianna_taborda I recall several community posts reporting this symptom (i.e., the status is missing / hidden) in the last few weeks. Please work with your Jira Site Admin to submit a ticket to the Atlassian Support team to have them take a look: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @ezra bibby and @Valerie Knapp Your rule uses Lookup Issues to gather the issues, tries to branch over the issue data, and then tries to modify the issues. That is what the error is indicating (even though it is poorly worded): the Edit Issue action needs an issue and one is not provided. Lookup Issues is used to gather…

Hi @Marc Parsons -- Welcome to the Atlassian Community! What do you mean by: {{issue.created.diff(now)}} This works but places it as a complex text string and will not add it as a number (of days) in the number formatted field at all. To get the number of days difference between created and now in an automation rule,…

Hi @Betany Riley FYI... The JPD dates are formatted as JSON, although they are recognized as text in rules. With the new function jsonStringToObject(), the dates may be more easily accessed with their attributes. For example, this would access the "start" attribute:…

Hi @Kate The JPD dates are formatted as JSON, although they are recognized as text in rules. With the new function jsonStringToObject(), the dates may be accessed with their attributes. For example, this would access the "start" attribute: {{jsonStringToObject(issue.customfield_11517).start}} And if you needed a different…

Thanks for that information, and... * Using the information from the current sprint name, you could extract the number "32" using text functions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ * That number could be converted to a number with the function…

Hi @Ponce de Leon, Eduardo -- Welcome to the Atlassian Community! Have you started an automation rule to do this? If so, and it is not working as expected, please post the following to provide context for the community to help: * an image of the complete rule in one single image for continuity * an image of the audit log…

Hi @Marine Redon Rather than using the JSON to repeatedly extract the value, I recommend using a variable to capture it one time (from the trigger value) and then using the Edit Issue and Labels field ... ADDREMOVE option to make the update. For example: * trigger: sprint started * action: create variable* name:…

Just to confirm, you did try changing the rule actor to your user, as you have Creator permissions? If you did, I am out of ideas for this one: the field seems supported by rules, the dates are in the correct format, and the JSON seems valid. You appear to be on a free license level, correct? If so, you cannot submit a…

Thanks for that information, @David Ortiz Bollain Please try to stay with one thread when responding. That will help others reading this in the future know if there are multiple possible solutions to the question. Thanks! When creating variables, I recommend not using names which could be confused (by a person or…

Hi @pclosas For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches,…

Hi @Fabian_Fischer3 -- Welcome to the Atlassian Community! As this is a very old thread, please create a new question (perhaps adding a link back to this one). That will ensure the maximum number of people see it to offer suggestions. When you post your question, remember to include: * an image of your complete rule in a…

Hi @Fatima AlZarooni -- Welcome to the Atlassian Community! I recommend creating a new question using "Ask a question" at the top of this page. When you do, please include the following: * what problem are you trying to solve * what have you tried * what did not work as expected Those will provide context for the community…

When the rule triggers, it could parse the list and get the first item. And when there are more to process, iterate the list to create the remainder by dropping the first one using {{^first}}{{.}}{{/}} with the iterator.

Hi @Dag Atle Stentad That error indicates there is no page present for the condition to test. The branch is over Tasks, and so its parent page is not available. I believe the only way to do what you ask would be using the REST API with the Send Web Request action a couple of times: * for the Task, get the page ID with the…

Hi @西村 仁 / Hitoshi Nishimura -- Welcome to the Atlassian Community! There are no built-in dashboard gadgets to display: a speedometer, a single number, or a generic bar chart. Here are the supported gadgets: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/ Please check the Atlassian…

Greetings! This is a duplicate of the article you already posted to market this product: https://community.atlassian.com/t5/App-Central-discussions/New-Feature-in-Timesheet-and-Invoicing-by-Zen-Filter-Issues/td-p/2947218 Please delete this post. Kind regards, Bill