Bill Sheboy Expert

You describe... * When you change the branch to most recently created issue * Some of the "done" issues still change to the status of "to do" Then something other than this rule is changing the issues. Please find an example issue moved from "done" and look at the change history to learn which user made the change: If that…

Would you please post images of your complete rule which does not work as you expect, and of the audit log showing the execution details? That may provide some context to uncover what is happening. Thanks! Also, are you using Jira Cloud or Server/Data Center?

Thanks for your complete rule image, Jerin. It does appear you are repeatedly creating new subtasks for the trigger issue, and then transitioning them to the "to do" status. All except the last one, which you leave in whatever the initially created status is. (perhaps backlog?) Again I recommend you change each branch to…

Hi @Danielle Campos That is not possible with the out-of-the-box features of Jira's JQL. Some possible alternatives/work-arounds are: * Check the marketplace for apps which enhance JQL or reporting * Check the REST API to pull data with the issue change logs * Call the REST API for the sprint report and parse the JSON into…

Hi @Manon Ledda Would you please clarify what you mean by: "The aim is to know how much my sprint cost me"? That may help the community give you suggestions to try. Thanks! For teams using the scrum framework, the team collaborates to deliver the items (i.e. stories) in order to meet the goal. Measuring by an individual…

Hi @Paul D'urso For your case #2, you could do that by making one or two rules for the updates, triggered on the epic's component changing. Using one rule could be a bit complicated, so the alternative is two rules: one that updates stories when the epic changes, and one that updates subtasks when a story changes. For the…

Hi @Tien Nguyen Your rules seem okay to me...and... There were some Jira and automation problems during that timeframe, which you may review here: https://jira-software.status.atlassian.com/ If you are no longer seeing the issue perhaps they were caused by delays or rules not triggering from the outage. Kind regards, Bill

I am glad to learn that worked! Please consider marking this question as answered to help others in the future searching for similar use cases. Thanks!

The answer depends on whether or not you expect your sprint names will contain spaces: * If no spaces: you may paste that expression into the Values to add for the Labels edit. It will appear below the field, so select it to set it. * If yes to spaces...You will need to remove the spaces first using a temporary variable*…

Hi @[deleted] That error tells you Labels cannot contain spaces, which is correct. Without seeing the details of your edit, I am guessing that you are trying to add to Labels with {{issue.sprint}} or {{issue.sprint.name}} The sprint field is a list, and when you use it that way it is split into individual values delimited…

Wait a second: in your image you are in the settings view on the left panel. Please select Back to Project to see how that helps.

Odd...I just tried toggling the new experience for the left-panel (under profile) and didn't see this symptom either so it does not appear to be the UX switch. Here is a relative link for the releases page for Jira Cloud, in which you can replace your company URL and project name to try:…

In none of your rule images do I see issues transitioned to "done" by the rule. Would you please try to post your complete rule as one image? That will confirm that we are seeing the same thing as @Mykenna Cepek and I try to help you. To do that, you may need to shrink your browser zoom, grab the image, and crop/scale it…

Hi @eirens From that left pane, when you navigate to Features and scroll down to Releases, is the option enabled or disabled? Kind regards, Bill

Jerin, let's pause for a second to confirm something please: * Are you trying to create a subtask and then transition that new subtask to "to do" * Or something else If it is #1 and only the new subtask needs to transition, you can change to branch on most recently created issue, and the problem with altering other "done"…

Hi @Talles Silva Put things outside the loop (iterator) that you want just once, and things inside to repeat with each issue. Perhaps try this: Prioridade Alta {{#lookupIssues}} {{#if(exists(priority))}} {{#if(equals(priority.name, "Alta"))}} * <{{url}}|{{key}} - {{summary}}> {{/}}{{/}}{{/}} Prioridade Urgente…

What I was describing was when you use a list iterator with smart values, only the child attributes (smart values) are referenced. Please see this documentation for examples with issue fields: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples You note the structure is…

Hi, Daniel. Yup, I got what you were trying to accomplish, and sorry I didn't clarify my suggestion better. The issuelinks from the Parent have only the key, and not the rest of their data, such as linktype. If all of that data was present, you could use list filtering to do what you asked. As that is not possible, I was…

Hi @Sam Harding Thanks for your insights and updates! Is there a work item/suggestion issue for the typing change to created variables which the community may watch for updates, or is this article the place to watch? And thanks to @Mykenna Cepek for driving toward clarity! (I'm guessing we won't find a Backus–Naur form…

Hi @Nils Kunze Adding to the ideas John suggested... Do you have a custom workflow, perhaps related to the status Discarded? If so, there is an open defect that when you have a custom event on a transition, the Issue Transition trigger does not fire. The work-around is to remove the custom event. Kind regards, Bill

Hi @Tyler Stephens What problem are you trying to solve? This is what I use to guide the automation rules I write... * If the problem requires a single atomic operation one rule is often better * If the problem can be split up to solve it in pieces without altering the intent, multiple rules may help with maintenance,…

Hi @Eugene Eng In your workflow are you using a custom event? If so you may be encountering this defect: https://jira.atlassian.com/browse/JRACLOUD-74614 Kind regards, Bill

Hi @Sharona Keren I do not believe there is anything in standard license, out-of-the-box Jira Cloud that can do what you ask. Some options to try are based upon your need frequency and cost/effort to invest: * Need infrequently, and little effort: export the data to a spreadsheet and perform the calculation and sort there…

Hi @pavlova_iryna When you note this "does not work", what are you observing? What is in the audit log for the rule? And when you iterate over the values in a list that way, you do not repeat the top-level: just the child attributes. For example (and I have not tested this as I do not know the response data structure):…

Hi @Kaj Sennelöv You are trying this for an initiative and epic, which do not have supported parent/child handling in automation yet (I think)...I know of one way to do this with automation: * Parse your labels to add from a list, and add them in one step with JSON, as shown…

Hi @Rajendra Borde You are using the issue created trigger, so there could be a timing issue where the data is not yet available when the event occurs. (This is a known problem for automation.) The work-around to solve this is to add a Re-fetch action immediately after your trigger and before any other rule components.…

Hi @Talles Silva You almost have it...please nest the filtering inside of the lookup, add a missing parenthesis, and check the name rather than the priority value. For example: {{#lookupIssues}} {{#if(exists(priority))}} {{#if(equals(priority.name, "Alta"))}} * <{{url}}|{{key}} - {{summary}}> {{/}}{{/}}{{/}} If you know…

In that case, please take your replaceAll result, and save that in a created variable, Then use other text functions such as substring() to pull that apart and put it into the jiraDate format yyyy-mm-dd, and Then try the conversion with toDate.

Thanks, @Mykenna Cepek ! I missed that part regarding the trigger. __Bill

Hi @Talles Silva Please take a look at this article on the filtering syntax for list handling/iteration: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Kind regards, Bill