Bill Sheboy Expert

Thanks for clarifying: your need is a feature request for the addon app for the marketplace vendor.

Hi @Karoline Rezende Ramos I have observed that error when the custom field is not on the edit view, the custom field is different type/value (such as for team-managed or multi-project rules), the rule actor does not have permissions for edit, and when the issues have been made read-only. Would you please post an image…

Hi @Susan Keithley Yes, and...to Trudy's answer: With an automation rule and custom field, you could simulate a progress bar...However with the resizable nature of board elements that may not lead to a consistent bar size display. Kind regards, Bill

Hi @Lakin Duplessis -- Welcome to the Atlassian Community! Please try branching to the new epic before adding the new stories. For example: * trigger: scheduled * action: create issue (for your epic) * branch: to most recently created issue* action: add story, with the epic link (parent) of {{issue.key}} as this will refer…

Hi @Wong If that is a variable, please try putting the quotation marks around the smart value instead: objecttype = "Contact" and "Team" = "{{vAssignedTeam}}" Kind regards, Bill

Hi @Ivan Andrieiev With Jira, estimates are made on issues (e.g. story) by users of the tool. And issues can be assigned to one user. The estimates are not assigned to a specific person (i.e. Jira user). What problem are you trying to solve? Knowing that may help the community to make some suggestions. Thanks! Kind…

Hi @DEEPAK KUMAR Tiwari -- Welcome to the Atlassian Community! Are you doing this only for the current, in progress sprint? If so, have you tried adding this to the JQL: sprint IN openSprints() Kind regards, Bill

Hi @Sreeram Panigrahi -- Welcome to the Atlassian Community! Would you please describe the problem you are trying to solve? Knowing that may reveal another solution for the community to suggest. Thanks! Kind regards, Bill

Hi @Jakub Stephan For a question like this, please post images of your complete automation rule and the audit log details showing the execution. Those will provide context for the community to offer suggestions. Thanks! Until we see that...I suspect you are either missing a branch statement or the trigger used doesn't…

Hi @Albert Manuel Please post images of your complete rule and the audit log details showing the rule execution. Those may provide context to explain what you are observing. Thanks! Kind regards, Bill

That is what I would expect if just using the conditions, and it is why I suggested either using the branch or if/else, as @Vamsi Kandala also suggested. For example... * trigger: your custom field changes * condition: issue type is not epic * branch: on the JQL I described to gather the selected values* action: link to…

Thanks for clarifying, and you are correct: unless the issues are created sequentially you cannot easily create the "blocks" links in your desired order. My idea of using a branch may not work if all the issues are in a chain. The reason is that automation rule branches on more than one issue run in parallel and…

Hi @Arlene.Amaya Yes, and...to Mikael's answer: Without knowing more about the specifics of those 31 linked tasks...I wonder if they can be created in single loop (i.e. branch) within a single rule. Perhaps if you share some details the community can offer ideas. Thanks! Kind regards, Bill

Hi @Mitchell McMahon I hypothesize the answer is: no, that value is dynamically computed when it is needed for display/reporting. Kind regards, Bill

Hi @Jennie Rosio -- Welcome to the Atlassian Community! Yes, and...to Nic's answer in case you are looking for source materials on those subjects. The one from Anderson lists the different variants of IT practices for Kanban, and lists the sources of those from the Toyota Production System and earlier.…

Hi @Dana.Harel You do not say how you determine the specific epics to link to for each value in your Department Involved field. Let's assume it is one of these * The epics have something in the summary (or another field) which associates them* Using an branch on the values in your custom field with JQL to find the…

What is not working as you expect? For example...if there is an error in the audit log please provide that message. If instead the rule does not work as you expect, please describe the symptoms you observe versus what you expect.

Hi @Varun Reddy Jonnalagadda -- Welcome to the Atlassian Community! The delete issue action deletes the "current issue", in scope at that point in a rule. Perhaps try branching to the specific subtask you want to remove and then use that action. If this is unclear, please post an image of your complete rule as that may…

Greetings! Without knowing the problem you are trying to solve, I am unclear what you are asking regarding a recommendation. The purpose of the rule image you posted is unclear to me, as it appears to create a subtask, and then repeatedly transition all subtasks to different status values in an unpredictable manner. I…

Apologies in advance for the long explanation :^) For branches on one-and-only-one issue (e.g. last created, parent epic, current issue) when the rule gets parsed and run, the rule steps runs in the order you see them. Essentially the code is "in-lined" with the loop "unrolled", in dev-speak. This has been confirmed by a…

Hi, community! As JPD seems based on Jira Team-Managed Projects, it is possible the current Jira Cloud incident is impacting this: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Sinisa Glusac To confirm the problem you are trying to solve...you only want the Parent to change to the earlier date if a Child issue has one. Is that correct? If so, couldn't you change your advanced compare condition in the branch to: * first value: {{triggerIssue.Start date}} * condition: less than * second value:…

Hi @Blair Would you please explain the problem you are trying to solve with that rule? Knowing that may help the community to offer suggestions. As your rule is shown...I would expect completely unpredictable behavior regarding sub-task status transitions. The reason is that branches execute for each issue in parallel and…

Hi @rie ajiki Mentioning groups is not possible yet with Jira Cloud. There has been an open suggestion to add this feature for many years; you may watch/vote for it to see any progress: https://jira.atlassian.com/browse/JRACLOUD-28225 Kind regards, Bill

Hi @Stefanie Sullivan I am unaware of built-in features to do this with Jira Cloud. How often do you need to do this, as that will help you decide how to proceed? For example... * infrequently needed:* review the issues manually at the end of each sprint, or... * export the issues to a spreadsheet and use formulas and…

Hi @Derek Owens -- Welcome to the Atlassian Community! I have seen several posts about this behavior before, and I hypothesize it is an accident/defect that it works sometimes. If nested branches were intended to be supported they would be in the documentation...probably with several articles written describing use cases…

Hi @Prashantha Kumari -- Welcome to the Atlassian Community! I suggest taking a look at this information on list filtering: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 And this one on the and() function for conditional…

Hi @Nita Sexton Yes, and...to Mark's answer: I recommend treating this cross-project board as view-only and only make updates to issues from the original boards. That will reduce confusion and possible errors due to the type differences, such as status and custom fields, that Mark noted. Kind regards, Bill

Hi @Susann Petzold Yes, and...to Mark's answer: One challenge is: what do you want the rule to do when multiple matches are found? Using the if/else structure Mark describes you will need to decide the order of precedence for assignment, such as checking "headset" before "network" before etc. One possible work-around for…

Hi @Dana.Harel There are at least two ways to do this, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ {{now.startOfMonth.plus(24)}} add 24 days to the 1st of the month = 25th {{now.withDayOfMonth(25)}} set the day of month, no matter when the rule runs, to the 25th…