Bill Sheboy Expert

Hi @Varsha Patel There seems to be a defect where community articles do not show the badges for Atlassian team members. Thus, people may skip over this one thinking its from a vendor or spam. Please consider adding your Atlassian role information at the top of the article to help people know its from Atlassian. Thanks!…

Hi @Anika Dixon There seems to be a defect where community articles do not show the badges for Atlassian team members. Thus, people may skip over this one thinking its from a vendor or spam. Please consider adding your Atlassian role information at the top of the article to help people know its from Atlassian. Thanks! Kind…

Hey, @John Funk -- The extra rules help with "belt and suspenders" for the ways I could think of (off the top of my head) which could lead to a change / setting of the Sprint field...rather than just with the manually triggered rule. For example, someone creates a work item and at the same time adds it to the active sprint.

Hi @Kurt Huhner First thing: for the rule you show, that will always try to transition the work item back to the same status it is currently in (i.e., a looping transition). Is that what you wanted? Next, what are the types of those fields: number, select-option, etc.? Next, I personally recommend never using the new-ish…

Hi @John Funk Reading the question / scenario and responses, I personally would not use automation rules to solve this one...although it is certainly possible. (Yes, I noted multiple rules as I guesstimate this would take at least five rules with the triggers: manual, work item created, work item moved, work item type…

@Gerda De Lima -- Thanks for the rule images, and... Please try to stay within one thread when responding. That will help others reading the question in the future know if there are multiple solution approaches. Thanks! For the rule you show and the scenario: * First, the Work Item Created trigger has racetrack timing…

Hi @Marc -Devoteam- Would you please clarify what you observed working with DC: * referencing outside data within a long-format iterator (i.e., using the issue prefix) * or something else? Thanks!

Hi @Gerda De Lima -- Welcome to the Atlassian Community! 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 trigger / actions / conditions / branches * an image of the…

Hi @Rachel Wright Thanks for your article series. Yes, and...for this one... My hope is one day Atlassian will improve / expand the features of the REST API endpoints for automation rules and add webhooks for rule events. For example, adding: * a "get all rules with details" endpoint * a "get component codes to…

Hi @Marc -Devoteam- FYI -- that linked question you provided is for Jira Data Center automation, not for Cloud (which this question appears to be). And for Cloud, I do not believe the {{issue.subtasks}} smart value contains all of the fields due to just-in-time read access, timing problems, etc. Thus, a Lookup Work Items…

Hi @Mateusz Janus Without seeing the details of all your rule actions, I see at least two problems with the rule you show: First, when using a long-format iterator such as {{#lookupIssues}} ... {{/}} inside of that, the issue prefix is not used as the scope is the lookup itself. Next, for Jira Data Center / Server…

Well done! And as a suggestion, you could use the and() function to reduce the chance of update errors by combining some things. For example: {{#if(and(totalScore.asNumber.gt(12), totalScore.asNumber.lte(18)))}}Medium{{/}} Then you would have four expressions, one for each possible value. One more thing: if you are using…

Thanks for the rule images, @Jamie Koch For the rule trigger, I recommend moving conditions directly to the JQL (when possible) to make the rule more efficient. And, as this rule runs daily you may want to use an additional condition inside the branches to check when an update is needed. That is, only perform the edit when…

Hi, community managers! Please move this question from the Jira area to the Jira Product Discovery (JPD) one to help focus the discussion on the JPD roadmap symptom. Thank you! https://community.atlassian.com/forums/Jira-Product-Discovery/ct-p/jpd Kind regards, Bill

Hi @Venkatesh Parthiban_G If you are on a paid license level, I recommend asking your Product Admin to submit a ticket directly to Atlassian Support to take a look. They will have better internal logging and can answer your specific usage questions for things not described in the Rovo documentation for use with automation…

Hi @Matev Iliya -- Welcome to the Atlassian Community! First thing: the "check for errors" in the rule editor can detect many problems, but it cannot detect complicated smart value expressions or things that go wrong when the rule runs. Please post an image of your entire Create Work Item action. That may reveal other…

Hi @Ivan Andrieiev There are risks when using an automation rule to limit work in progress (WIP) by moving items to another status...such as unintended consequences. For example, people may decide to not update Jira and continue working on other items regardless of status selected; then the board no long reflects reality.…

Thanks for that information, @iotim as it indicates some things to try... First, when accessing a checkbox field's values, that is a list of values...not a single value. The expression you show might produce a list of true / false values, and thus not work as expected. Next thing, if the contains() function actually works…

For existing work items, you could try a rule triggered on a change to either custom field...or a Scheduled trigger rule with JQL testing that both fields are not empty. Then the rule conditions could check if the values meet / do not meet your criteria. The Scheduled trigger approach could help identify items already…

Hi @Kent Robbins Please try this smart value when the rule trigger is Page Commented: {{comment.author.emailAddress}} And...some Confluence smart values are not well documented, so it can help to check both the Jira smart value documentation and to use the Log rule action to write expressions to the log for some…

Hi @iotim For a question like this, context is important for the community to help. Please post the following: * Are you using built-in checkbox fields or a marketplace app / addon for the field? * An image of your complete automation rule in a single image for continuity * Images of any relevant steps accessing the field…

Hi @Kurt Huhner -- Welcome to the Atlassian Community! There is no way to compare two fields using built-in JQL searches, although marketplace apps which extend the features of JQL may help. And, with built-in features, the values of one custom field cannot be limited based upon the values in another field during add /…

Inserting NOT within the CHANGED operator's clauses, or adding a list of values for FROM, TO, etc. is not supported. There are lots of related suggestions in the JAC backlog which you may watch / vote for to see progress: https://jira.atlassian.com/secure/Dashboard.jspa For the specific query you note, one workaround is to…

Hi @User12345 Please provide an example JQL where the NOT keyword does not work as expected with those additions to the CHANGED operator. Here is an example where NOT is used with CHANGED AFTER: project = MYPROJECT AND NOT status CHANGED AFTER -120d ORDER BY Key ASC And, often a JQL query's logic may be inverted to provide…

Thanks for that information, @mark_overdijk You have posted this question in the Atlassian products community, but your question seems to be about Microsoft Power Automate features. I recommend checking any community / support for that product (i.e., Microsoft Power Automate) to learn why all of the Jira spaces are not…

Thanks for that information, @Kristína Salaj as it shows the cause of this symptom: The image you show for the Send Web Request action includes your work item field, and that likely contains the URL to the Confluence page...However, the apparent suggestion from Rovo describes the approach I described, except they list a…

Hi @Kristína Salaj 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 *…

Hi @Lindsay Filz Yes, and...to the information from @Hamza Chundrigar and @Julia Foden about this unhelpful UX change: Here is the release note item for the change, and I recommend periodically checking both it and that community article mentioned by Julia to learn if Atlassian either rolls back the change or adds a…

Did you try using the custom field ID in place of the field name in the JQL? That will confirm if the problem is the wrong field is being accessed. To find your custom field ID, let's use a REST API endpoint: * identify an example TMP work item with your field where it has data in it * when logged into Jira, open another…

One more thing to check, aligned with the ideas from @Marc -Devoteam- Unfortunately, there is nothing in Jira to prevent creating multiple fields with the same names, both globally (i.e., company-managed) and in team-managed spaces. And, it is possible to accidentally select fields at different scopes within a…