Bill Sheboy Expert

Thanks for that clarification...and... You seem to be measuring something for individual people when a Scrum team usually works collaboratively to share the work. Doing this could lead to unintended side-effects and problems for the team. It may be helpful to instead have discussions with the team if you have concerns…

Hi @Bolaji Jegede Would you please clarify a bit as that may help the community to offer better suggestions? Specifically, what is your "percentage of resolved" ( X of Y possible) based upon: * all issues resolved within a window of time * all issues resolved for children of an epic (or linked issues) * all issues resolved…

"These go to eleven." This is Spinal Tap

The key difference between the Scrum and Kanban boards is that the Scrum one only displays issues in the current/active sprint. Team may add other criteria when sharing a project, as I noted using component or label field values. Board name is not a field or anything which can be queried. If you want to use JQL (outside of…

Hi @Omprakash Thamsetty I suggest using the actual hour counts for the day ranges you want. That will avoid any issues with working day/hour calculations that Jira may do. For example for during 10 days ago from "now": project = myProject AND created >= -240h AND created < -216h AND statusCategory != Done As needed, you…

Hi @Pooja Heda To save you some time of ideas that do not work for this use case, automation rules are unable to detect the change to/from a sub-task for issue type...and according to this timed-out defect, Atlassian does not plan to fix this issue based on their current…

Hi @Pravin Gurung What marketplace addon app are you using to manage your Behavior-Driven Development (BDD) features? Once you know that, please ask your site admin to contact the product's vendor to ask this question as they will probably know your answer. Kind regards, Bill

Hi @Shirley Yes, and...to what @Sagar Mahajan suggests: Would you clarify your planning steps a bit, as that may provide context for the community to offer ideas to help? You ask about using JQL to find issues for the next sprint to support sprint planning. Sprint planning is normally when teams identify and select work…

Hi @Shobith Devan Could you push from the apps using an incoming webhook trigger to an automation rule and then update your tests? https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#Automationtriggers-Incomingwebhook Or, similarly pull using the webrequest action and a scheduled trigger:…

I am glad to learn that helped. Please consider marking this question as answered. That will save other people time finding solutions in the future. Thanks!

Hi @[deleted] -- Welcome to the Atlassian Community! Do you mean for automation for Jira rules? If so, I do not know of a way to do that yet. Rule management is not apparently logged in the admin site logs, and there are no public REST API functions yet for managing automation rules. Kind regards, Bill

Hi @[deleted] -- Welcome to the Atlassian Community! Please try the IN statement, such as: project IN (myProject1, myProject2) AND... Kind regards, Bill

"Move Issue" trigger doesn't execute when moving issues to same project https://codebarrel.atlassian.net/browse/AUT-1526

Awesome! And I believe that as you have implemented the rule with branches, it may also handle the case of issue type conversion/move: sub-task to story, or the other way around.

Thanks, Alex! I last tried that with changelog about a year ago...I think. Did you test that rule with a move operation? How about with company-managed versus team-managed as they have different parent handling?

Thanks, Andy. I look forward to learning how this can be improved over time. Certainly any unexplained search results create work for customers and the support team answering their questions.

Hi @Chris Waller Adding to John's ideas... You cannot perform that check/query with out of the box JQL. You could do probably do it with a marketplace addon for JQL. As a work-around, you could detect this condition using automation rules. For example: * trigger: issue field fixVersion changes * condition: issue type is…

Thanks for clarifying. Based upon the time-tracking tool your Jira instance is using, that field is computed from logged time. So you cannot re-purpose it other than by altering the tool/addon used or change which values are logged.

Hi! I tested this a while ago, and can confirm that you cannot yet detect in a rule when the parent changes as it is not supported in the changelog. To be clear, the "issue updated" trigger can fire, but the changelog does not record the parent change. @Parcandi Administrator Is subtask count a custom field you are…

Hi @Katie Schneider Yes, and...to what Nic asked about: You note when you checked the history, it showed a specific person/user. That could still be from automation if the rule actor was changed. Have you reviewed the automation rules/audit log in the project and at the instance level to see if there were any rule…

Hi, Mykenna! For the possible deadlock, I was noting the path of parents can change children...and children can change parent's dates. Which could lead to either rule looping or rules not firing when the engines "runaway" detector halts processing. For the manual "tampering" scenario, we had a similar case when we used…

Hi @Marco To do this without an SLA, you could use a scheduled trigger and JQL to find the issues which have not changed status. For example, this JQL finds any "in progress" issues which have not changed status in the last 24 hours. project = myProject AND NOT status CHANGED AFTER -24h AND statusCategory = "In Progress"…

Hi @Tijs Tijert Yes, and...to add to what @Mykenna Cepek suggests: * Incrementally building this is key, as automation rules have no source control. Build one part to get it working and tested, and then copy that rule, disabling one of them, and continue work on the copy. Then you can revert if the rule gets too broken. *…

Hi @Berat ÇOLAK I suggest that you review your automation rule and its audit log, comparing them to the details of the Jira issue which does not process. That should reveal what is happening, such as the issue not meeting certain rule conditions. If you are still unable to uncover the cause, please post images of your…

Hi @Dominique Hermens Would you please post images of your complete rule and the audit log showing details of the execution that does not work as you expect? That additional context may help the community to offer ideas. Thanks! Kind regards, Bill

Hi @Raghu Nekkanti -- Welcome to the Atlassian Community! Would you please clarify a bit what you are trying to accomplish? That may help the community to offer suggestions. * What do you mean by "candidate" and how is that different from "engineer"? * Your team appears to have a Scrum Master and PM. Why are either one of…

Hi @Jim Stewart -- Welcome to the Atlassian Community! Yes, and to what @Jose Luis Gaitan suggests: You note forecasting based upon what is in the backlog, perhaps using the built-in reports. Please check the report you are using to see if it supports use of Quick Filters. If it does, you can easily ignore the non-MVP…

Hi @Parcandi Administrator Yes, and...to Alex's suggestion: You do not show an image of your current rule, so it is difficult for the community to give you focused guidance. Please consider posting your rule to help provide that context. Thanks! Regarding your second question: depending upon your current rule, you may not…

Hi @Cesar Daldosso To get the latest end date for any sprints for an issue, please try this: {{issue.sprint.endDate.max}} As the sprint field is a list, the max() function will return the value you want. Please note: In your rule, the sprint field could be cleared and trigger the rule, and so this would lead to old values…

Hi @[deleted] How often do you need to run this query, as that may help you decide possible solution approaches? One time: Run your existing query without the "commented on" check, and... * Manually look at issues histories and comments, or * Export the issues to a spreadsheet and use formulas to identify the last comment…