Bill Sheboy Expert

Hi @Breanna Williams @Mikael Sandberg answered why your second rule was not triggering. And I wonder: why do you have two rules rather than creating the subtasks with the task in the initial rule? You can do that by branching to the most recently created issue (after creating it) and then add the subtasks. Kind regards,…

Hi @Tom.Hext -- Welcome to the Atlassian Community! I am assuming you are using Advanced Roadmaps (timeline) as you appear to be on Jira Premium. Is that correct? If so, when the sort order has not been set, it uses the default: Rank. That also is the default for the filter when creating a Jira board. In that case... * If…

Hi @Singh, Gauraw -- Welcome to the Atlassian Community! If your list of values is frequently changing, and you want these values in a custom field, selection list, what do you want to happen when a value has been selected in the past and it is no longer in the updated list? What is the purpose of this custom field?…

Hi @Frank Adding to Trudy's answer: once you have stored your conversions in the Lookup Tables, you could use those in math operations to calculate the result: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Kind regards, Bill

One challenge with a scenario like this is automation rule branching: branches run on more than one issue run asynchronously and in parallel, and there is no guarantee when they will finish...up until the very last step of the rule. I believe there are suggestions to add a "wait until completed" for branches, similar to…

Some of the fields in advanced roadmaps are not available in automation rules yet. That is why I was suggesting trying your JQL stand-alone with Advanced Issue Search first to confirm it works as you expect. For example, the initial rule seemed to return too many Features for the trigger issue, Epic. Would you please post…

Hi @Björn Out -- Welcome to the Atlassian Community! Depending upon your custom field type...I wonder if you could use your webhook data to iterate and build a JQL statement (with an IN statement, or a bunch of OR statements, or...) and then branch to that for the updates. Using a branch will be constrained by automation…

Hi @Adam Quinn -- Welcome to the Atlassian Community! I do not believe there is a built-in, automated way to export the users. As alternatives you could investigate the Atlassian Marketplace to search for an addon, or you could build something using the REST API for user management: *…

Thanks for that information, and as a tip: please try to stick with one thread in responding. That will help others see if there are multiple possible answers to a question. Okay, looking at the rule's audit log, it seems to be showing multiple issues where found that are parents of the trigger issue Epic. Is that what you…

Hi @jeroen_wilmes When something with parent/child relationships does not work with JQL in lookup issues, the cause may be the context of the rule action (i.e., where we are in the execution). To help diagnose this, would you please post images of your complete automation rule, including the details of your lookup issues…

Thank you for that rule image. You noted earlier getting this rule from a template, and I believe you are using this rule from the project's templates: When a task is new due --> send email reminder. The two different calls to Lookup Issues with similar JQL have two different purposes, helping to send each assignee one…

The reason I asked to see an image of the rule is what you describe is not possible: nested branching in automation for Jira rules. And so I believe we are not aligned on how you are describing the rule and my understanding of it. Seeing the rule will confirm that. Without seeing your rule... I hypothesize you are seeing…

Yes, the watcher field is a multi-select user field.

The image I see in your post is showing the blue shaded area for the standard deviation, as described here: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/ Do you have an image which shows the chart and which does not show the blue shaded area, as you described? Thanks!

Hi @Luiz Eduardo Freitas Santos Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide context for what is happening, as I suspect this is either a branching or a variable scope issue. Kind regards, Bill

Thanks for confirming your project type as there are known problems with accessing the People fields in team-managed projects to send notifications. Here are a couple of the defects/suggestions around that symptom: https://jira.atlassian.com/browse/JSWCLOUD-20774 https://jira.atlassian.com/browse/AUTO-519 I am going to…

I think it is the same as this automation issue for Server/Data center version, even though you appear to be using Jira Cloud https://jira.atlassian.com/browse/JIRAAUTOSERVER-159

Hi @Nick McCue -- Welcome to the Atlassian Community! Would you please post an image showing the symptom you describe, where the Atlassian interpretation of standard deviation is not displaying on the page? Kind regards, Bill

Hi @Sheri Widler Not all of the fields from advanced roadmaps are supported by automation rules, and I believe there are several fields called "team" in Jira... So first thing, I recommend using this how-to article with example epics and stories/tasks to confirm the fields are supported with smart values in automation…

Hi @tyrone kimble Do you mean using an automation for Jira rule? If so... No, that is not possible directly from an automation for Jira rule. If you have a REST API method that could be called which provides the data from the CSV file, that could be called from a rule to do as you ask. However it would have a limit of the…

Hi @Vijaya Lakshmi Speaking from my personal experience of doing that: yes, the data will remain unchanged. The only changes would be how you choose to configure the user roles and groups, and your billing license level. Please review this excellent article with step by step instructions on changing from the Beta. I…

Hi @Laura Thorsvik -- Welcome to the Atlassian Community! Adding to the other answers provided, Atlassian provides some free online training for using JQL to answer questions like yours. Please look here for more information: https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql Kind…

Hi @Maryam Yusuf As that appears to be a paid-license marketplace addon product, I recommend contacting the vendor's support to ask this question. Here is their marketplace support page for more information: https://marketplace.atlassian.com/apps/1219205/scrumpy-planning-poker-for-jira?hosting=cloud&tab=support Kind…

Hi @[deleted] -- Welcome to the Atlassian Community! First thing, there is a JPD community group and so you may want to look over there for similar questions/ideas: https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery Next...How your teams work may better influence what you need. I…

Hi @Yaniv Bernhard You appear to be using the StonikByte Great Gadgets addon from the marketplace. Is that correct? If so, the behavior you observe is correct because this gadget shows the Work In Progress (WIP) aging, and the first column of your board is a not-started condition and the last column is a done condition.…

Hi @Giulia Quaglia -- Welcome to the Atlassian Community! Are you using a Company-managed or a Team-managed project? You may find that information at the lower-left of the expands area of the screen. To mention someone in a comment (or other text field), please use this format, substituting in your custom field…

I note your JQL is referencing issuecount but your new entity property key is named sprintcount. Even with that change, I also am not able to get this to work with JQL, and cannot find my earlier saved examples. It appears I used the entity property manager (free marketplace addon) to originally get the field searchable.…

You could use an entity property for that; rules can set/read them and they would not be on the screen. Would you explain further: why do you need to save the value when you want to notify the changed users each time?

Hi @denis.sheridan I was able to do that in two steps... * Copy your table to a created variable to convert it from an object to text. Let's name that varCopyOfTable * Extract the keys from the resulting text version of the table:* {{varCopyOfTable.split(",").match("(.*)=.*")}} That works by splitting the table rows back…

An entity property can be set at various levels, including for the issue. And automation rules can set a property using an action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Set-entity-property So let's say you add a property named sprintcount to the issue, and in the rule the value is set…