Bill Sheboy Expert

Awesome; that helps identify the cause: please note in the audit log how the value from the dropdown is surrounded by brackets (either as text or as a list). And so the comparison of: The test of "[3] greater than any number" will always be true because it is performing a text comparison and the left-square bracket […

Given what you describe, certainly try to build the rule to save your teams time and reduce errors. And if you run into challenges, please post the following for context so the community can offer suggestions: * an image of the complete rule in one single image for continuity * images of the trigger, actions, conditions,…

Thanks for that information! Have you tried writing the form field to the audit log to confirm it contains what you expect? What is the type of your form field? I notice the first two conditions both test a value greater than 2. Is that correct?

Seeing what you tried will help to rule out (no pun intended) potential problems and identify what prevented the rule from working. The most basic rule to do this would be: * trigger: work item transitioned to "Done" * condition: work item type is "Dev Task" * branch: on JQL to the other sub-task -- parent =…

Hi @Dan Foster A smart value may be typed in for the parent field with the Edit Work Item action, although it is not obvious how to do so: * type in the smart value * when it appears below the field, select it for use More importantly, I do not recommend using an automation rule to change the work item type, particularly…

Hi @Erica Robinson For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution Until…

Hi @Jo-Lee Bertrand Would you please post images of the following to provide more context: * your current, complete rule in a single image * images of the trigger, and of any actions, conditions, and branches * an image showing the audit log details for the execution, remembering to expand all of the areas at the right…

Hi @Lesly Cracchiolo For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions /…

Thank you for clarifying the scenario. There is a template in the rules list you could start with named: When all sub-tasks are done → move parent to done With that as a starting point, you could change the Related-Issues Condition to use JQL (rather than just checking the subtasks), and then copy it so both subtask cases…

As a precaution, you may want to put a 0 as a default value at the front of that expression: {{#=}}0{{#lookupObjects}}+{{Amount}}{{/}}{{/}}

The only other things I can think of to check are: * If you are using a marketplace addon gadget, perhaps check with the vendor * If you are on Jira Cloud and the site was migrated from a Server / Data Center one, I have heard of problems with historical information impacting JQL searches If it is neither of those cases,…

Hey, @Darryl Lee -- I must have been typing that up whilst you were mentioning me :^)

Hey, @Bud Herz The keys for updating of the previous Epic's values for most of those cases are: * only include the parent field with the Field Value Changed trigger, and * that will allow using the changelog smart value with the {{fromString}} With that, you may access the previous Epic's key to make the changes needed.…

Hi @Bud Herz I do not have a specific answer to why the counts are different, and I wonder... The AFTER expression with the CHANGED operator uses a date value only, and there is nothing documented about the time part. I wonder if the time zone is causing the differences in which date is used. If you examine examples of…

Hi @Kelly Bates For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches…

Hi @Sara Beyer Using a branch will probably not work for this scenario: branches which could be on more than one thing are run in parallel and asynchronously. The impact for your rule is the multiple updates could collide, intermittently succeeding or failing. A better approach is to perform one single update of the work…

Hi @Mehak Bokhari Thanks for this great addition to rule actions! This may save people an additional call to the REST API to update the content of newly created pages. On the topic of content, what will be accepted in the Page Content field: plain text, HTML, markup, the same raw content as for the REST API endpoint, etc.?…

Hi @Jacquelyn Mosby When your rule is triggered on a change to that specific field, you may try using the changelog smart values to detect a value was added, and only send emails to the added users. This may be the fastest / simplest approach to implement. However... There are known defects with the accuracy of changelog…

Hi @Mathew Lederman There is a new REST API endpoint specifically to help get user information, regardless of the profile visibility setting. As a disclaimer, I have not tried it yet: Please look here to learn more: https://jira.atlassian.com/browse/ID-7744 Kind regards, Bill

Hi @Rick Dorgan Unfortunately, the Data Center version does not have lookup tables yet...which would make this scenario easier. Until then, I can think of two ways to do what you ask: conditions and conditions + variables. Conditions: use branching and conditions to add the watchers, one by one. This is the slower method…

For a JPD date field, those are JSON stored as text, and so the values may be extracted for use as dates using the jsonStringToObject() function: {{jsonStringToObject(issue.myJPDDateField).start.toDate}}

Hi @Anette Noll What problem are you trying to solve? That is, "why do this?" Knowing that may help the community better understand the need to offer better suggestions. Until we know that... What type of project is this: company-managed, team-managed, JPD, etc.? What is the triggering event for your scenario as your rule…

Hi @Kris Dewachter Branches which could be on more than one thing are executed in parallel and asynchronously. And so that variable will not be repeatedly updated as you might expect. Instead, each re-create of the variable is thrown away when that pass through the branch finishes. Worse still for your scenario: the steps…

Thanks for clarifying the scenario, and... When you want to selectively add one or the other Component, please use an if / else block in your rule to make that decision with conditions.

I agree, and I am glad to learn you found a new endpoint to find the information.

Hi @SilkeS Did something change for the Notification feed (under the bell icon) with this release? It now shows intermittently as empty with the message: You have no recent activity. For those of us who do not use email notifications, we rely upon that feed to find / review activity. Thanks!

Hi @Brian Richardson -- Welcome to the Atlassian Community! Jira Scrum boards consider a work item as "completed for the Sprint" when it is in a status value that is mapped the far right board column. Otherwise, they are not considered completed and move to the backlog or next sprint, depending upon what was chosen. Did…

Hi @Bud Herz Yes, and...to John's suggestions: your license level and desired level of accuracy determine how to implement updates like this. For example, let's assume you have unlimited rule usage and want the data as accurate as possible, as quickly as possible. There are a bunch of scenarios to consider for accurate…

Hi @Adam Bang Yes, and...to the other suggestions: I recommend sharing the following information rather than providing your rule's JSON export: * an explanation of what problem the rule is trying to solve * any known exceptions / gotchas for the rule, including maintenance needs * an image of the complete rule, in one…

Hi @Eric Segui Haugli -- Welcome to the Atlassian Community! I believe your last paragraphs outline what is needed for this scenario using built-in features: * an automation rule triggers based on some work item (formerly called "issue") change * the relevant Confluence page is identified * call the REST API endpoint to…