Bill Sheboy Expert

You appear to be on a server version (as you cannot see a Jira version with Cloud...it's is just whatever-they-released). And because can select the Version Created trigger, you are on the advanced (paid) version of Automation for Jira, rather than lite (free) version. I suggest starting with the Version Created trigger to…

Thanks, and I believe Target Start is one of those advanced roadmap fields which has some oddity with automation rules. Other built-in/system fields like that are indeed text and not date or date/time type, and so the conversion was needed. (Another example is the Status Category Changed Date, which is text for a date/time…

To level set a bit, are you using Jira Cloud or Server/Data Center? And if using Server/Data Center, which version of automation for Jira are you using? For Jira, the items you see on the "Releases" configuration are used in the version fields for issues, Fix Version and Affects Version. So one is used by the other. When…

Hi @Walter Buggenhout Is the "filter counts" gadget you are showing from a marketplace addon? Thanks! Kind regards, Bill

Yes, I believe either approach would work.

What is the type of that custom field? If it is not date type, you could add an asDate conversion before making the adjustment.

Hi @Jeffrey Bistrong Please try using minusDays() instead of minusDay(), as I believe all of the plus/minus ones use a plural name for the units of measure: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Kind regards, Bill

No; if you want to clear a field, select it for edit and leave the field empty/blank.

Thanks for that information. First thing, I recommend mapping out all of your scenarios as this will help determine what is (or is not) possible with automation for Jira rules. With that noted, there are two triggers that you might use if you flip the way you think of the scenarios...What if you detect when the version is…

Hi @Tracy Brigham You posted this question in the Jira software area, and seem to be asking about Trello. Is that correct? If so, consider posting this in the Trello question area: https://community.atlassian.com/t5/Trello/ct-p/trello Kind regards, Bill

Hi @Lucas Silberberg Yes, that should be possible. You would use the Issue Transitioned trigger, selecting the correct status values, and then edit the Start Date field, setting it to {{now}} Kind regards, Bill

Hi @Fong Xu -- Welcome to the Atlassian Community! Would you please describe the problem you are trying to solve? Knowing that may help the community to make suggestions. Until we know that... Let's assume you want to do something with issues assigned to a release. In this case, you could gather the issues (with another…

You would substitute in the expression I noted earlier. For example, the one for the remove would be this: {{#changelog.labels}}{{#fromString.split(" ")}}{ "remove": "{{.}}" } {{^last}}, {{/}}{{/}}{{/}} And then inserted into the JSON update would be: { "update": { "labels": [ {{#changelog.labels}}{{#fromString.split("…

Using those exact same created variable names, I was not able to reproduce the symptom you are seeing. However I do not have advanced roadmaps and so cannot replicate the same JQL you are using in the lookup issues actions. I wonder if this is related to the advanced roadmaps feature of JQL you are using. In any case, I…

Hi @Frankyzhou The documentation page Walter provided for the control chart shows examples of these symptoms, with the first chart showing issue clusters, the 24h day, and variation in predictability. The second chart showing the change in the y-axis. These are how this Atlassian chart works, so there is no normal or…

Hi @Patrick Hicks Would you please show the actions which create those other two created variables? Those may reveal the source of the symptom as it appears the values are getting parsed as when the rule editor attempts to save this action. I hypothesize from the names that those are counts from lookup issue action calls,…

Hi @Alexandra Astor Adding to Nic's suggestions... Without seeing the details of your rules' issue edit actions, I wonder if the edits of the two merged rules could be done with one branch and one issue edit action. * The branches are different (one is on "clones" and the other is on "clones" or "is cloned by") so perhaps…

Hi @Anil Adding to Mikael's answer: you appear to be using Jira Server version, and so here are the automation references for that version: https://confluence.atlassian.com/automation/smart-values-993924860.html https://confluence.atlassian.com/automation/examples-of-using-smart-values-with-lists-993924631.html Kind…

Hi @Fuji Are you using a Company-managed project (CMP) or a Team-managed project (TMP)? You can find this information at the bottom-left side of the page in the expanded area. Where was the custom field "actual end date" created? The reason I ask these questions is that custom fields can be defined at a global scope for…

Hi @Frankyzhou -- Welcome to the Atlassian Community! Yes, and...to Walter's answer, here are some potential things to watch for Atlassian's interpretation of a control chart based on my process analysis experience: * When multiple items have the same measure, they get rolled up into one value (large dots for a cluster of…

Hi @Maham Nadeem -- Welcome to the Atlassian Community! Adding to Trudy's answer, here is the how-to documentation for making a JSON edit like that for multiple-user fields: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-user-picker-custom-field Kind regards, Bill

Hi @Giannis Michailidis If I understand your question, you want to compare two different issue fields with JQL. That is not possible with out-of-the-box features: JQL is not a SQL. Your possible work-arounds depend upon how often you need to perform this query and if you have (or can buy) addons: * need one time* export…

Hi @Richard Williams Looking at your results, there are multiple rows with the same total. As those dashboard gadgets have only one sort field selectable, I hypothesize that the order after that point is either random or is different for the two gadgets. For example, several rows have totals of 52 and of 19 for what is…

@Tanguy Crusson ...yes, I know it seems I asked this question earlier :^) And now that I can see the actual changes it seemed unclear due to this in the role selection: Where it seems the project admins, "Administrator" in this new role model, can add and change roles of users, and so impact licensing costs. And...there is…

Hi @Tanguy Crusson Thanks for the update...and...just to be clear... From what I am seeing, a Site Admin will need to be set up as a Creator to manage users (and their role) for a JPD project...even if they do not plan to administer the project or to create ideas. Correct? The alternative is we delegate user management and…

Hi @Karthika Murugesan You could iterate over the Watchers field to add each one as a mention, as described in this thread. However...If they are already watchers, why would you want to do this? Kind regards, Bill

Thanks for that information, @Adam Ziecik As you noted you are using the Server/Data Center version, there are no created variables and so that syntax cannot work. Specifically, you cannot use {{varRemoveLabels}} and {{varAddLabels}} Instead you need to replace the created variables in the JSON expression with what was…

I recall seeing an experimental REST API to get the options, but I cannot find it. One way I know works is to set the option you want in an issue, and then call the REST API to get the possible smart values, search for your field, and you will find the option id, as described in this how-to…

Would you please post images of your complete rule, including the details of the issue edits with JSON, and of the audit log details showing the rule execution? Those may provide context for what you are seeing. The JSON I noted earlier worked for the original question and for Jira Cloud, so something may be different for…

I am glad to learn that helped. When I wrote that one, I just did some quick testing around your scenario. Please try the different cases you expect to confirm it works.