Bill Sheboy Expert

Hi @Elisa Cerri E Cerri -- Welcome to the Atlassian Community! Are you asking about seeing the time in each status? If so, you may see that with the built-in control chart report: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/ Unfortunately that report has some limitations.…

Hi @Ivan Shtanichev To do that dynamically, you could call the REST API function from the rule using a web request and then parse the response using list and text functions to get the component list. This will slow down the rule, perhaps by several seconds. Kind regards, Bill

Hi @Julia Foden Without seeing your rule, I suggest the answer is "maybe". Please take a look at advanced branching for options to iterate over the values from a list. (You may use list functions and the CSV values you note to drive the branching.)…

Hi @Markku I do not believe that is possible with out-of-the-box Jira Cloud. And I didn't find any open suggestions to add the feature. There may be marketplace addon app gadgets which support this: https://marketplace.atlassian.com/ Kind regards, Bill

Hi @mini There is an open defect for this symptom for team-managed projects, when querying on the default status values: https://jira.atlassian.com/browse/JRACLOUD-77518 Kind regards, Bill

Hi @Kristie Tokifuji I am unclear on what you are asking; perhaps you could answer some follow-up questions to help the community offer you suggestions. * Are you using a marketplace addon app for test management, or did your team add an issue type for tests, or are you just using the built-in types (e.g. story, task,…

Hi @Jay Keck -- Welcome to the Atlassian Community! There is an open issue for this symptom in the automation backlog: * https://codebarrel.atlassian.net/browse/AUT-1134 Kind regards, Bill

Hi @Nick Jennings You are correct: there is nothing in out-of-the-box JQL as it is not a SQL. There are marketplace addons which enhance JQL to do this. If you just need this once for a few issues, you could try exporting the issues to perform the comparison. Kind regards, Bill

Hi @Tiberiu Cristea Yes, and...to what Trudy suggests: Do you actually have a status named "Resolved"? If so, that could lead to some confusion in the future as I believe that is a system-defined value used to indicate the date/time an issue's Resolution value is set. Kind regards, Bill

Hi @Ekaterina Georgieva -- Welcome to the Atlassian Community! For a question like this, please consider posting images of your automation rule and the audit log. That will provide context for the community to offer ideas. Thanks! Given what you have described, I believe you could either use advanced branching or…

Hi @Mike Downing -- Welcome to the Atlassian Community! First thing, I am using Cloud and not Server/Data Center. My first guess is no: you cannot access the Start Date for a fixVersion from smart values. I checked the REST API and the method below to learn what smart values are available, and Start Date was not included:…

Hi @Colum McAndrew For teams I have supported, going over "WIP is the leading indicator for lead time..." doesn't help without additional chats to progressively build up knowledge. Instead we stick with simpler ideas on the impacts of task switching, knowledge silos, WIP debt, and Age of WIP. Some teams I support have…

That seems curious...Two more things to check: Please check and post an image of your workflow to see about that status which is not used. Please try creating a new board in the project directly from the filter, and see if it displays the issues.

Hi! I recommend trying something like this: * trigger: version released * branch: for issues in version* action: transition to done A lot about automation rules is experimentation. So please try to create a rule first and when you have challenges getting it to work, post images of your rule with your question; then the…

Hi @Denis The Lookup Issues action only supports a small number of fields currently, and does not support those time tracking fields. I believe using the REST API is one of the only ways to do this currently from within a rule. The other way is to trigger on child issue changes for the fields, adjusting custom fields in…

Hi @Kazumi Kerr -- Welcome to the Atlassian Community! You are describing splitting down a rule with over 100 steps, and then triggering those rules sequentially. I wonder if all of the steps you note are one atomic operation, or if there could be separate rules triggered on changes made...or even better, utilize the…

Hi @kspeight I am having trouble understanding what you are trying to accomplish. Would you please post images of your rule (including JQL details, audit log, and conditions) and explain how it is not working as expected? That may provide more context for the community to offer suggestions Thanks! Kind regards, Bill

Hi @Sel Some things to check for this symptom for a company-managed project Kanban board: * What is your board filter? If you use that filter stand-alone in advanced issue search, does it return what you expect? * Is there a Kanban sub-filter set (at the bottom of board settings/general)? If so and you remove it, what…

Ah! Smart values are usually case sensitive, and unfortunately do not show errors when you get the case incorrect. The smart value for Lookup Issues uses camel-case: {{lookupIssues.size|0}} Please change your condition and see what happens.

Hi @Christine P. Dela Rosa Did this research include information for *the same teams* over time, including any changes to location, or only sampling teams based upon the current working norms: co-located, all remote, or hybrid locations? It would be interesting to learn how team health changed (or didn't!) independent of…

You are using Cloud, correct? If so, perhaps do this in two steps to force the type conversion to string: * create a variable and set the value to the temp_Asset_ID * then perform the charAt() on the variable I recall needing to do this for other fields which are dynamically generated before I could use them in expressions.

Hi @Harpreet Singh -- Welcome to the Atlassian Community! When you started the sprint (date/time) were the stories sized with story points? If not, the total was zero (0) at the time the sprint started, and so was the "commitment" for the report. In that case, a tip is to complete your sprint planning/sizing before…

Hi @zsamai -- Welcome to the Atlassian Community! Yes, and...to what Trudy suggests: Please have your site admin check your subscriptions, and perhaps contact their support team here: https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud?hosting=cloud&tab=support We are using Great Gadgets for Jira…

Hi @Krupa sagar -- Welcome to the Atlassian Community! How do you want to update these issues? For example, let's assume you wanted to transition all of these issues to "done". You could use an automation rule to do this, triggered on the version release. Kind regards, Bill

Hi @Hari Kotty -- Welcome to the Atlassian Community! Your JQL on the Lookup Issues action is trying to match the wrong field. Please try to match to the key from the epic (the branched issue) issueType IN (Story) AND "Epic Link" = {{issue.key}} Kind regards, Bill

Hi @Nishant Paraskar I have not seen more than a few seconds delay for manual rule execution except when there is an outage, and the status page looks okay currently: https://status.automationforjira.com/ Would you please post an image of your manually triggered rule? Perhaps the issue is in the rule processing and not the…

Hi @[deleted] This appears to be a global/multi-project scope rule. Is that correct? Would you please show the details of your edit action? To link an issue to the epic, you normally set the Epic Link field of the child item (your trigger issue). If that is not what you are trying to do, would you please clarify your use…

Hi @Amroz Please consider using the if/else component with your summary and other conditions. Then you could enforce this workflow progressively, one condition set as a time for the new sub-tasks. Of note: by waiting to create the sub-tasks you could be creating a condition where the team cannot see the full planned work…

My apologies as I left out a key piece! When you want one rule to cause triggering another, in the second rule, go to the Details and enable the option Allow Rule Trigger. Otherwise the rule engine detects this as an error and will not fire.

Hi @Davis Moes That branch you note would not find the sub-tasks. You could either: * create another rule, triggered on label changes to the stories, to copy down to their sub-tasks * in the original rule, extract all of the keys of stories in the epic into a created variable list, and then create another branch on JQL to…