Bill Sheboy Expert

Hi @vincenzo.spatafora -- Welcome to the Atlassian Community! I do not have that information, as I am just another user with no knowledge of Atlassian planning. I recommend watching this suggestion to see progress, or working with your Jira site admin to contact the Atlassian support team to ask for their…

I am getting a bit lost on the changes you are making which are helping / not helping. My recommendation would be to: * post an image of your entire rule in one image, providing overall context * post an image of any specific actions * post an image of the audit log details showing the rule execution * restate the scenario…

Thanks for that link, Jordi. I suspect the limitation is for JSON data which is not for an issue...or more specifically, which cannot be iterated over as a list with attributes. Another workaround would be to use a dynamic regular expression with the match() function.

Awesome; I am glad to learn that helped! Regarding documentation, I recommend posting feedback on the documentation pages and from the automation rule editor. Many of the differences for TMP versus CMP are subtle; some are not ;^) Giving feedback on what we find will help Atlassian understand the impact to customers and so…

Hi @Jenny Finneran Adding to John's ideas... Would you please post an image of the audit log? And, looking at your JQL in the trigger, is that correct? It seems to be checking for "NOT status changed 2 minutes in the future" as the value is positive, not negative, relative to "now". Kind regards, Bill

Hi @Support IVèS I respectfully suggest not changing an issue's type in an automation rule. When an issue type changes, many things need to be checked / updated, often leading to prompts to the person to guide the change. This is why Jira has a specific app function in the UX for this: Move. An automation rule cannot stop…

That field would not be human-readable...and copying it would likely break things: the rank value for each issue in a site is unique. Repeating my earlier ideas: * The REST API function is needed to programmatically update the rank field * Please discuss what you are trying to do with your Jira site admin for their input

Hi @Damien Lepage There are several open suggestions related to that idea, and some posts in the original article on Lookup Tables asking for sharing / reuse: * https://jira.atlassian.com/browse/AUTO-472 * https://jira.atlassian.com/browse/AUTO-736 *…

Although it may seem like a lot of info, here is some documentation and free training from Atlassian to help learn more about creating JQL to solve your team's needs: * https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/ *…

Hi @Wilf I do not believe there is a built-in dashboard gadget to show counts for different filters. There are certainly multiple marketplace addon gadgets to do this type of reporting. You do not show your filters, yet note they differ by issue type and status. Have you reviewed the filter criteria to learn if they could…

Hi @Girish Hippargi and @Trudy P Claspill The People-type field in Team-managed project (TMP) have some challenges in rules...and this appears to be one I did not know: They appear to be multiple-select behind the scenes and that checkbox for "Restrict to single user" only impacts entry on the issue views. I confirmed this…

Hi @Maela Aseglio You may have the incorrect smart value for the field in your expression. Smart values are name, spacing, and case-sensitive, and sometimes the smart value does not match the exact displayed field name on the Jira pages. When an incorrect smart value is used, it is replaced with null, often causing no…

Hi @Rihab BENYOUCEF There are at least two open defects in the public backlog for this symptom: https://jira.atlassian.com/browse/JRACLOUD-70797 https://jira.atlassian.com/browse/JRACLOUD-81443 I would expect the impact to be worsen if anyone has created a team-managed project in your Jira site. If the symptoms you see are…

Hi @Anuj Gupta -- Welcome to the Atlassian Community! Short answer: no, there is no supported way. There was / is an deprecated REST API function to do this, but I would not rely upon it to continue to exist. Instead you could try: extract the data you need from logs, build your own app to do this, gather data after sprint…

Hi @Piotr Nowak Do you have a known list of projects to group by? * If so, you could use smart value, list filtering with the single lookup inside of the branch to do this, with a filter for each project: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 * If you do not have a…

Hi @Jordi Romera 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.…

Awesome; I am glad to learn that helped! On automation knowledge, I agree the documentation has gaps and continues to improve over time. My ways of learning about this product are: * Experiment...a lot :^)* I recommend creating a test project (and possibly a free account site) to try new things, with less risk of harming…

I believe that is possible, although I am not a ScriptRunner or Behaviors user and so cannot confirm that. Perhaps check their docs or wait for another community member who uses the product to post ideas.

Hi @Jill Vieregge 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 @Erin E -- Welcome to the Atlassian Community! First thing...for older threads it can help to create a new question and add a link to original ones. That helps ensure more people see the question to offer suggestions. Back to your question... You can use various conditional logic functions to do that, such as not() and…

Hi @Chiara Squilloni As that symptom appears to be from the marketplace addon, I recommend continuing to use their support team to address this. Kind regards, Bill

Hi @Samuel Chebook -- Welcome to the Atlassian community! Yes, and...to Trudy's suggestions: The image you show is the boilerplate JSON that shows for the Issue Create or Edit Issue actions, and it is normally only used / validated when someone has made an edit to the JSON. Unless you need JSON for your rule action, please…

Rules have a limit of 100 issues for a trigger, branch, lookup, etc. in a single batch, and so this may not work for your scenario due to the issue created trigger. What problem are you trying to solve by linking together that many issues: what is the "why"? Knowing that may reveal other solution approaches.

Hi @Abir Brahem What problem are you trying to solve by doing this? That is, why do this? Knowing that may help the community suggest additional ideas. Until we know that... It is possible to call a REST API function to set the rank of one (or more) issues relative to another issue. And so the rule would need the key for…

Hi @Guilherme Bombonato Vaz de Mello I believe the Rank field still uses the "Lexorank" algorithm, producing an alphanumeric string to enable easy add / remove / modify of the order of issues without changing all other issues. That field is not directly edited, but it can be modified using the REST API functions. You seem…

Hi @Revathy -- Welcome to the Atlassian Community! In your rule, your log action uses {{issue... but it should use the {{lookupIssues... smart value. Regardless of that problem... Unfortunately, the Lookup Issues action for Jira Data Center version does not support most fields yet, including the time tracking…

Hi @Timon Karge-Lücker -- Welcome to the Atlassian Community! Sorry for the long answer, as I have also spent lots of time on this automation behavior of determining emptiness. I will add bolded text to help focus the ideas I suggest. First thing, are you using Jira Cloud, Server, or Data Center version, as automation rule…

Hi @Jake S Have the team and its leader considered using observation, discussion, and existing practices to do this? For example, agile teams typically have some forms of planning, daily standup, and retrospective. And so everyone should know forecasts and progress of work, and feel empowered to speak up if they observe…

Hi @mokupuni919 -- Welcome to the Atlassian Community! Automation rules cannot have nested if / else conditions, where one is inside of another. There are three alternatives to solve the scenario you describe: * Review the JQL for your different queries to determine if it can be merged in such a way that there are only two…

Hi @Pete Robbins From what you describe, you have a rule in place which is triggered by the addition of labels to issues in the SWdev project and then creating issues in the relatedDocs project. And now you want to add those specific labels to the issues. If that is the case, what is not working as you expected? For a…