Bill Sheboy Expert

Hi @Özge Özgenç A variation of the other suggestions is to use a Lookup Table action for this need: https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333 With that, you could create keys that represent the concatenated values of the priority and severity names (as…

Hi @Bent Möller First thing, I doubt that is supported behavior and may stop working (or not work as you expect.) I recall similar community posts about multiple levels of nesting for if / else blocks and branching, using drag-and-drop for incompletely defined actions. Often such rules would fail to work as expected or…

Hi @Chen Qiu What have you done thus far to solve this need? For example, have you tried creating the rule or reviewed the documentation for that trigger type: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Incoming-webhook Kind regards, Bill

Hi @Mathieu Hebbrecht -- Welcome to the Atlassian Community! Adding to Walter's answer... That symptom is a known issue with the way the gadget dynamically adds to the JQL for the time series. You may read one example of that defect…

Hi @Andrew Wilks -- Welcome to the Atlassian Community! You note this: There is an ask for us to assess how we can reduce the number of sub-task tickets that are created - without losing our ability to monitor. What is the problem being solved by reducing the number of sub-tasks? That is, "why" do that? Knowing this may…

Hi @Kiran Kumar For a question like this please post an image of the complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Until we see those... You are trying to compare data value using a text formatted version of the dates. When doing that,…

Hi @Jeevan Kumar K G For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Kamil Askerov Adding to Rebekka's suggestions: You could use conditional logic to only include the assignee mention when it has a value. Please look here to learn more about that technique: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ Kind regards, Bill

Hi @koutarou ishibashi That is not possible yet, and there are a couple of suggestions in the public backlog to add it. A work-around, to avoid manually updating the list of user account id values, would be: * call the REST API function to get the group's users with the Send Web Request action * parse out the account id…

Hi @Kamil Askerov You do not show this in your rule details image, but I suspect you have enabled the "Allow Rule Trigger" option, and because this rule adds comments it triggers itself...which seems like a bad idea for this scenario. Please try disabling that option. Kind regards, Bill

Hi @Jesus Octavio Gutierrez Villegas First thing: this is a very old thread, and so I recommend creating a new question rather than adding new ones onto it. That will help more people see it to offer suggestions. Thanks! Regarding checkbox fields, that depends upon what you mean by "checkbox field": * If it is the built-in…

For this technique with one-and-only-one-thing branches, I recommend using a different variable name. There is no documentation of the expected behavior when shadowing a built-in smart value name. Regarding branch execution with could-be-more-than-one-thing, there have been several community posts from Atlassian team…

I am glad to learn you have something working, although 27 if / else blocks may be tricky to maintain. I recommend regularly checking the audit log for that one to watch for problems.

I think you can still use the Issue Linked trigger for that one. For your scenario(s), the key is which issues are checked / branched to. If you post images of your current rule and audit log details, that will provide content to make adjustments. Thanks!

The syntax looks correct (without testing it myself), and I recommend adding a write to the audit log for {{branch.name}} before the condition and confirming it contains what you expect.

Earlier I noted rule scope, and for a rule to access issues in multiple projects, the rule must be global or multi-project in scope. Is your rule project-scope only? If so, your Jira site admin will need to help change the scope.

First thing: please review that audit log as it shows two different custom field id values for "sponsoring product/area product" * customfield_30502 when the issue edit is attempted, and fails * customfield_14503 when the transition is attempted, and fails This indicates there are at least two different fields with the…

Based on what you describe, there appears to be an addon application logging the time, versus an automation rule. I recommend talking to your Jira site admin to learn about that addon, learn how it is intended to function, and then contact the vendor's support team on the marketplace for help.

You could call the REST API function to get the project, using the Send Web Request action, to determine that: https://community.atlassian.com/t5/Jira-Software-questions/REST-API-How-to-get-project-type-Next-Gen-or-Classic-from-quot/qaq-p/1444777

Hi @Per Carlén Context is important for automation rules. The symptoms you note could be caused by where the smart values are accessed within the rule. For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details…

Hi @karim -Atlassway- Why do you keep posting the same boilerplate text to promote this product for questions when it is not relevant to the questions asked? For example, you note restoring deleted labels but the question did not ask about deleted labels. Kind regards, Bill

Hi @Romeo Bollen That is showing the day-of-year ("D"), and not the day-of-month ("d"). When looking at the documentation for automation functions, they often also provide links to the supporting materials. In this case, there is also a link to the Java documentation which shows the possible format layouts / characters.…

Hi @Dan Driscoll Yes, and...to the suggestion about possibly combining the rules and using if / else condition blocks... After the changes to the automation limits / packaging, project-scope rules no long have unlimited usage executions. You appear to be using a standard license, and so combining the rules will help manage…

Hi @Amal_Hoetmer Although what you describe is possible with an automation rule, I wonder how this impacts the team's use of Scrum and sprints. When using Scrum, teams plan a sprint using their expected capacity to achieve a goal. Such teams, particularly ones who also have production support responsibilities, reserve some…

Hi @Diana Dvorska What purpose / value does the label provide? For example, is it meant to be a visual indicator when the labels field is added to the backlog view? Instead, have you tried using a quick filter with JQL to just view the older issues: created <= startOfDay(-180) Kind regards, Bill

Hi @LIS Guy Knowing what problem you are trying to solve (i.e., why do this) will help the community to offer better suggestions. Until we know that... The only way I know to prevent such linking is to not use any team-managed projects (TMP) by removing that permission from everyone except site admins. Of course, if one of…

Hi @Jayashree Ramesh -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, why do this? You mention Great Gadgets, which is an addon for Jira dashboard visualizations. What will you do with the percentage: display on dashboard, send a message, report somewhere, or something…

Hi @Victor Tobon -- Welcome to the Atlassian Community! What is the custom field you are copying the value from, and what is the current value of that field? For example, is it a number field, or is it something else? Kind regards, Bill

Just to confirm, you want those linked issues which are only in the STIN project, correct? If so, please change the JQL for the first lookup issues action to this: project = STIN AND issue IN linkedIssues({{triggerIssue.parent.key}}, "relates to") And then the second lookup is not needed.

Hi @Rafa Have you tested this suggestion you propose? I wonder about it: * There is no concept of "global scope" in a rule; it is all about context within the rule structure * The technique described looks like is overwriting a built-in smart value, but instead that actually creates a new one with a duplicate name. There…