Bill Sheboy Expert

Hi @Kyle Williams -- Welcome to the Atlassian Community! Atlassian's interpretation of a control chart shows the issues based upon: * the board filter (which is the basis of their reports), * the selected status values, * any quick filters selected, and * the time range selected. If you are missing some information, I…

Yes, and...I am with @Mykenna Cepek on the suggestion to contact support for those JQL anomalies you are seeing. They could look at logs we cannot see to offer suggestions. There is always in-progress work on JQL and the REST API, and so you may be seeing problems that others have not found yet. Thanks!

What have you tried putting in the "matching JQL" field? What is happening when it errors out? Please try: statusCategory = Done

Hi @lhz -- Welcome to the Atlassian Community! You are correct that there is no built-in trigger...Instead consider using a Issue Transitioned trigger for the first issue, and then find the predecessor based upon how they are dependent. For example, when using issue links for dependencies you could use JQL to find the…

Hi @Gray Webb Yes, and...to Andy's ideas: If the powerup is consistently adding a label in that format, you could find those labels using an automation rule...which could then add something that you can query upon. For example, let's assume you are only adding issues to one project in Jira from Trello. Then in that…

Hi @amit_bakst If the "Team" field you are describing is for advanced roadmaps, you may only be able to access that using JSON as the fields are not shown in the rules dropdown lists yet. Here is the suggestion to add that capability: https://jira.atlassian.com/browse/JRACLOUD-77431 Until that is available, you can try a…

Hi @Katarzyna Kaźmierczak -- Welcome to the Atlassian Community! How are you distinguishing defects which are independent of the sprint's work versus ones related to the sprint's work? Knowing that may help with creating your dashboard. For example, when using a bug sub-task type for ones resulting from a sprint's work,…

Hi @Peter Pshenichny -- Welcome to the Atlassian Community! Have you tried checking the attribute state for the sprints to find the active one using smart value, list filtering? For example, please try writing this to the log: Active sprint: {{#issue.sprint}}{{#if(equals(state,"active"))}}{{name}}{{/}}{{/}} Here is more…

Hi @Doug Levitt Yes, and...to the ideas from @Matthias Gaiser _K15t_ ... There are several open suggestions to add monitoring and REST API functions for automation rules, and any of these could help with health checks: * https://codebarrel.atlassian.net/browse/AUT-999 * https://codebarrel.atlassian.net/browse/AUT-1541 *…

Hi @Antonio Calì -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. As Nic notes, you cannot currently use automation functions to directly access the issue history (other than an elaborate work-around calling the REST API).…

Hi @Muhammad Azzazy -- Welcome to the Atlassian Community! Two of the automation improvements since this post was created may help: * created variables can now be used inside of functions * smart value lists can be filtered using other smart…

Hi @ED DevOps D2 Short answer: I believe you are going to need to implement this yourself, perhaps repeatedly checking if the due date is impacted by holidays and increment appropriately. Longer answer: * Currently the automation rules do not use the working and holidays configured in projects. According to the…

Hi @Fredrik Ivansson Flinta I recommend reviewing this documentation page and its examples for how to format the JSON for the different Jira field types: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ To confirm your source and target data, also consider looking over this how-to…

Hi @Larissa Fernandez -- Welcome to the Atlassian Community! Your use case is a bit unclear to me, and to solve this I suggest that you draw out an example timeline and scenarios. That will help you decide how to create conditions such that rule runs as you wish. For example, you appear to want to: * Check for issues with…

Hi @Dennis Neumayer With three boards (and backlogs) for the single project, you no doubt have different criteria to distinguish the issues. For example, components or labels. If you review that criteria and your board filters, you can determine what to change in an issue so it moves to the other one. Kind regards, Bill

Thanks for that information, @[deleted] Honestly I am surprised that works, as errors often occur for the opposite situation: trying to edit a field with a rule which is not available on the views. Have you tried a work around to clear the field, such a remove the existing value from the field?…

Of note... When you call the REST API with search and JQL, do you see the comment data? It is present when I call this for the search method with JQL. Next, if you do not add the project to your JQL, this could return multiple sprints across different projects, and this may not be what you wanted.

Often that is not possible, because the rule would potentially need to load all of the data for any linked issues in a chain...even if not needed. Instead you could use a branch to that parent to access the data, as I suggested for the edit, or Lookup Issues with the same JQL. Please note this gets more complicated if you…

My apologies if I was unclear...I do not believe it is possible to edit/clear a read-only field with the automation rule. If a rule could change such fields you have configured to be read-only, that would defeat the purpose of making them read-only. What are you trying to accomplish by changing a read-only field? Knowing…

Hi @Jyothi Ravipati One way to do this is with the built-in automation rules. For example, you could create a rule such as: * trigger: issue transitions to Done * condition: issue type is subtask * branch: on the parent of the issue* action: create the new subtask To learn more about automation rules, please look at this…

Hi @Mark Herbold -- Welcome to the Atlassian Community! You cannot do most of the things you ask with out-of-the-box JQL. Specifically, JQL cannot compare fields or create calculated fields for an issue, as you could with a SQL. Some of those queries are possible with a marketplace addon to enhance JQL features. Please…

Hi @Tim Cadran -- Welcome to the Atlassian Community! Perhaps the key here is you note this is for a quick filter. Is that correct? If so, quick filters only filter; they do not order the issues. Only the main filter for a board orders the issues on the backlog and the board. Kind regards, Bill

Hi @Hayley Rodgers Is this a project or global/multi-project scoped rule? Can the selected project see those status values? Have you also checked the issue transitioned trigger to learn if it can see those status values? Kind regards, Bill

Hi @Hayley Rodgers I am seeing the same thing with a company-managed project workflow, with Chrome and Edge browsers. Kind regards, Bill

Hi @[deleted] -- Welcome to the Atlassian Community! I suspect the answer is: no, that is not possible. A field can be made read-only using screen schemes and removing the field from screens used after issue create (e.g. edit). To modify the field later (with user edit, automation, etc.) would require it to be on the edit…

Please try changing the Condition to "all match specified JQL" to see that option.

For some other smart value, documentation improvement ideas please look here: https://jira.atlassian.com/browse/JIRAAUTOSERVER-103

Hi, Max. Thanks for adding more information! First thing: I recommend implementing this one-rule, and one-status at a time. Once you have it working you can decided if/how the rules can be merged. Next, some follow-up questions: * How many issues are linked for blocking: one-to-one, one-to-many, or many-to-many? * If…

Hi @yuliia.soury Are you using Jira Cloud with the Standard or the Premium license? If you are using Premium, there may be something in advanced roadmaps to help with this. For Standard license, what you ask may be possible with an automation rule, although it would be a bit slow to run and a bit complicated to maintain.…

Hi @bindu shree That REST API method for a JQL search should include any comments which are in the issues. The JQL to return issues in the current open (active) sprints would be as shown below. Please substitute in your project name and try this in advanced search to confirm it returns what you expect, and then use it in…