Bill Sheboy Expert

Please try to stay with one thread in posting your responses. That will help others viewing this question in the future to know if there are multiple solution approaches. Thanks! Back to your original question... If we assume you are adding all of these subtasks with one automation rule, I recommend setting the values for…

@Yannick-Noah Raubuch would you please post an image showing the audit log details for the rule execution? That may provide some explanation of what is happening. Thanks!

Hi @Noa Tsruya If you do not have the additional marketplace apps noted in the other responses, you can set the priority value using an automation rule, using conditions, lookup tables, or a combination of these. Note you will need two rules: one triggered on issue created (to set an initial value) and another triggered on…

For a trigger on a field change, you may use the changelog fields to find the previous value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- And I just learned something new: after(?) the changes for the epic fields, the parent field does not work for the changelog. Instead the…

Have you confirmed that new sprint (i.e., S&O 8) is for this board / backlog / filter, and not for another board in the same project? Are those active sprints (e.g., 3.24.0) for this board or for another one? I am using Jira Cloud, not Server version, so perhaps the behavior is different, although the documentation…

Hi @Åse Nordberg Adding to Walter's answer... When helping with another question recently, my testing showed issues do not need to be resolved (i.e., have a value in Resolution) to be in a released version. Using the dialog to release the version and selecting the option to "ignore unresolved issues" leaves them assigned…

Rules trigger when an event happens. This is why I noted earlier you would need at least 2 different rules: one triggered on issue create, and another on the transition to Done. I want to confirm you understand that, as rules do not run for a while, stop until some other event happens, and later pickup where the paused.…

Hi, John! I am on a free license now and thus no longer able to submit suggestions, so I posted here instead :^) Plus...even when I was on a Standard license, it appears customers cannot add suggestions to the AUTO backlog. They can only add to JIRAAUTOSERVER or to the several Jira Cloud-related projects...hoping the…

@Kalyan Sattaluri for this type of rule, the scheduled trigger should have no JQL, and thus that checkbox option has no meaning. Please re-read the original question / symptom and the linked article the poster provided to learn more about such automation rules.

Hi @Jack Brickey First, I agree with your ideas about story points usage. And... @Vineet.Kotian asked about setting the Due Date from the Start Date. Your example seems to show the opposite: adding to the Due Date. Kind regards, Bill

Hi @arjun -- Welcome to the Atlassian Community! Please check your Scheduled Trigger, as it should have no JQL. Otherwise it will loop for each user multiple times. The rule uses the Lookup Issues action and the branch to iterate over the users, and not the one from the trigger. I also noted a typo in your Send Email…

I am glad to learn that helped. And...to avoid the extra math expression wrapper, you can divide inline: {{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}}

Well done! This is one of the challenges of the highly-configurable permission features for Jira: the out-of-the-box permissions for automation work because they are elevated...but, if the project's lower-level permissions have been altered curious side-effects occur. And as we observed in this case, the app is "working as…

Hi @Lukas Niechziol -- Welcome to the Atlassian Community! JQL is not a SQL, and so does not have many features like joining queries. With saved filters, they can be combined with AND or OR using their saved identifiers, such as: filter=12345 AND filter=67890 There are marketplace addons which extend the features of JQL.…

Hi @Prajakta Amraotikar -- Welcome to the Atlassian Community! You are using a team-managed project, and configuring the fields on the backlog view and cards on the board is not possible yet. Here is a suggestion to add that feature, which you may watch / vote for, to see…

Greetings community! When writing commentaries / interpretations of the Agile Manifesto and the Principles behind the Agile Manifesto, I respectfully suggest: * providing links to the original sources, allowing readers to compare what was stated versus what was interpreted; and * not leaving off portions of either from the…

Ah...Has the actor for the rule been changed from default, Automation for Jira? When you tested that JQL in the branch, it is definitely uses the permissions of the person editing the rule. When it runs, it uses the actor. If you change the rule actor back to Automation for Jira and re-test, what do you see?

Would you please post an image of your complete current rule, in one image? Perhaps I am missing something we can see in the full context. And, please check your custom fields to determine if there are multiple fields named Parent. You can ignore the one named "Parent Link" if you see it; we are checking for "Parent". I…

Hi @Pierre Leroux Those fields are not from the built-in features of JQL. Both numberOfAttachments and LastAttachmentDate appear to be from the ScriptRunner addon from the Atlassian Marketplace. Perhaps check with their documentation or support to understand this symptom. Kind regards, Bill

Hi @Sierra Gaynor -- Welcome to the Atlassian Community! Yes, and...to Julie's answer: If you decide you want to try automating what you ask (i.e., setting a JPD idea's date field with a date from a Jira issue), please note that JPD uses its own version of a "date field". Those contain two dates (start and end), stored as…

Thanks for that information and image! When the Subtask was converted to a Task, it "moved" to the backlog, and you may find it there. Subtasks are parts of other issues, like Tasks. Thus the Subtask was never actually on the board...it only displayed there because its parent did. The fix: the Subtask can be added back to…

Hi @Gonzalo Galdames -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, why do this? Knowing that may help the community to offer better suggestions or alternatives. Until we know that... * What does the number represent in the subtask's summary? * What happens to these…

Hi @Lord Pablo You could try adding a Related Issues Condition, with JQL to check if there are no issues which are in futureSprints() which match your summary. For example: project = yourProjectName AND sprint IN futureSprints() AND summary ~ "\"Deploy to Development\"" This is checking for the specific phrase "Deploy to…

From that image, I see that is a team-managed project, and so the filter is not edited by the team. (For company-managed projects, teams have more control over what displays on the board, including adjusting the filter.) You show a subtask, MARKCRE-836; is that one of the ones converted to a task? If so, that shows a…

Hi @Quinn Bell -- Welcome to the Atlassian Community! What is the filter for the board? What is the status value of the task, and is that status mapped to a board column? It is possible the converted task does not match the board filter, or that the status is not showing on the board. Kind regards, Bill

Hi @Curt Cavazos 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 ideas.…

Hi @Katie Swanson-Wikelius 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 @Suzy Rothwell Please try using WAS IN for a list of assignee values: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN Kind regards, Bill

Hi @Tobias Sjöndin There are two potential problems with your rule... Your smart values are incorrect as they should use the time tracking data: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.timetracking-- And so first try this:…

Hi @dhanarajanr -- Welcome to the Atlassian Community! No, that is not a capability of automation rules. What problem are you trying to solve by doing this? That is, why do this? Knowing that may help the community to offer better suggestions. Until we know that...some potential work-arounds are: * Perform the polling /…