Bill Sheboy Expert

Hi @Sai Manisri Balmuri -- Welcome to the Atlassian Community! As @Sebastian Krzewiński noted, that is not possible with the Issue Statistic gadget as it needs defined values and the Story Points field is a number (not a defined list of values). I hypothesize you are trying to create a histogram by sizing, perhaps like…

Hi @Justine Flegler -- Welcome to the Atlassian Community! I do not believe there are built-in features to do that. Instead you could use your browser print-page functions or investigate marketplace apps for reporting. Kind regards, Bill

Hi @Jenna Clegg In your rule's scheduled trigger, below the JQL, is this option selected: Only include issues that have changed since the last time this rule executed If so, is that what you want? If not, disable the option and re-test by trying to run your rule manually under the ... menu with "Run Rule". Kind regards,…

Hi @Vivek Chaudhary -- Welcome to the Atlassian Community! I am unfamiliar with the term "phase" relative to issue types. Where are you observing this term in Jira Cloud? Kind regards, Bill

Hi @Laurie Sciutti I have not used the Atlassian approach of a "Dependency Mapping Play" nor have I experience with shutting down a company using the play, and... I have performed dependency analysis for various program / project / development planning needs, and one thing I note is missing in the play that your situation…

Hi @Viviane da Silva Moreira There is no trigger that is a schedule AND a status transition. What you could do is use the Issue Transitioned trigger and then use date / time functions with a Smart Value Condition to check the value of {{now}} to learn if it is within your scheduled…

Hi @Francisco Navarro What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post the following to provide more context: * what problem is your rule trying to solve; that is, "why do this?" * an image of your complete rule * images for any rule actions where the field…

If your site admin cannot see it, the Atlassian Support team can disable / delete the rule for you. I suspect that once you downgraded from Premium, even your site admin will not be able to see the rule.

Hi @Cash Coyne My understanding of that error is it's related to the service limit, where a rule cannot trigger itself or other rules more than 10 times in "quick succession": https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ I have found no documentation on what "quick succession" means as a…

Hi @Maggie Soria -- Welcome to the Atlassian Community! There is nothing built-in which can report on when the Due Date field value was set, even though that information is in the issue history. Some possible workarounds are: * I suspect there are marketplace addons to provide that type of reporting * Use a custom field to…

Hi @Craig -- Welcome to the Atlassian Community! I am guessing you mean a Confluence automation rule, correct? Are you on some level of paid license still? If so, please work with your Jira Site Admin to contain the Atlassian Support team to help with the rule: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @Diane Fahr As the JQL for your conditions and the branch are dynamic (i.e., based on some variables and data) I recommend adding writes to the audit log to confirm they contain what you expected. For example, before the Related Issues Condition you show, perhaps write this to the log: JQL for Related Issues Condition:…

Hi @JCameron Please take a look at this post yesterday from the JPD team about: As a first step, we're implementing the concept of "issue type", and "relationships" between these issue types...…

Would you please post an image of your complete rule, an image of the action using that smart value, and of the audit log details showing the rule execution? Thanks!

Hi @Peter Hiross I do not believe using variables that way is possible with JQL, and... Have you considered using chained filters on the page? For example: create one saved filter with your Fix Version test: project = myProject AND fixVersion ~ "19.0.0* Get the identifier for the filter; let's assume it is 12345. And so a…

Hi @Mike Siciliano -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Your Send Web Request action appears to be calling the wrong endpoint. Instead use the issue search, passing the JQL as a parameter: https://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/search-search

Please see the article I linked to for advanced branching; your rule should use that to iterate over the users in the field rather than use For Current Issue.

If that field is a user, please try using {{initiator.name}} instead.

Hi @Tanguy Crusson Thanks for this update! What can you share about how the linking / types of links will work for this feature? For example, will it be a new link type, use "Polaris issue link" with "implements", or something else? Knowing that will help automation rule writers account for this change in any existing…

Hi @Rafael Freymueller Well done solving the problem with the rule! And...please consider updating your rule to use Lookup Tables rather than the if / else blocks with conditions. That will make your rule much easier to maintain and to see such problems in the future. Please look here to learn…

Hi @joscha.reinhard -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Jacob Dressler -- Welcome to the Atlassian Community! After you edit the trigger issue, add a Re-fetch Issue action to reload the data before the rule proceeds. That will ensure the latest update to the field is used when you branch to the linked issues. Kind regards, Bill

Sorry, I do not currently have Confluence automation in my instance, and so I remembered it incorrectly. Please try using Lookup CQL Results instead: https://support.atlassian.com/cloud-automation/docs/actions-in-confluence-automation/#Lookup-actions

Hi @Wakil BENAMOUR Do you mean the custom field id for the field? If so... There are several ways to find that information. One is to call the REST API from a browser tab, with your example issue, to find the id: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ And please note well,…

Hi @Martin Vali For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @MF -- Welcome to the Atlassian Community! I recall the 100 email limit for the Free license level spans all emails sent by the site for any notifications and automations. https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/…

Hi @Kat Crawford -- Welcome to the Atlassian Community! Would you please post an image showing your board configuration, with the status mapping to columns? Jira Scrum boards (and burn charts) consider an issue "completed" when it is in a status mapped to the right-most column of the board. The status category (which shows…

First, for the CONTAINS ~ operator with JQL, you may want to use the exact phrase syntax for matches: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CONTAINS---- For example: summary ~ "\"PIM: Review\"" For the uniqueness checking, do you mean the Reporter of the issue will be distinct each time, or…