Bill Sheboy Expert

Hi @Shaun Hall -- Welcome to the Atlassian Community! Short answer: I recommend using split() and get() text functions to extract the values for your label creation, and then adding them using a JSON expression. For more information... In the documentation for the match() function, it describes this (with italics added by…

What changes are you making to the Description field? Perhaps you could add an additional condition to check if that change has already been made to avoid duplication. For example, using a Smart Values Condition to check if it contains specific text.

Thanks for that information. Please try creating that second rule to learn how it helps.

Hi @[deleted] The Jira user's account ID is different from the Slack user's ID. The Slack ID values are not stored in Jira. From what you show, it appears someone tried to add the Slack ID values as entity properties for each user, but the value is missing from one or more users. Atlassian wrote an article a while ago…

Short answer: I would not rely upon the order in the field to match your scenario needs. When entering all the values at once as you did, perhaps it is ordering them in the field. But it is likely in their "internal ID order", the "release order", or just the order you added them. And if values are added later, I doubt it…

Hi @Joshua Markus Quite recently, additional validation was added to the automation rule editor. When changing a rule, it is possible it cannot be enabled when it contains errors...but it can still be saved. I wonder if that validation is now checking when trying to enable from the rule list. Perhaps this rule has errors…

Hi, Trudy! To me, it wouldn't necessarily be better / worse. I just liked the "puzzle to solve" ;^) I do wonder about the "why" for cases like this...that is, "why would independent, cloned Jira issues need to be kept in status-sync across projects if they are truly independent work items?" And if they are not independent,…

Hi @Pfohl Jason Using a second rule with the Field Value Changed trigger for the Components field, one could detect using the field changed smart values for the specific values added, and use a Smart Values Condition to test that…

Hi @david_napoli , @Trudy P Claspill , and @Walter Buggenhout A single rule way to probably solve this, although a bit complicated, is using a Lookup Table to get the transition ID for the destination status (based upon the project) and then use the REST API called by a Send Web Request action to perform the specific…

Hi @Ray Nixon For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions / branches, and * an image of the audit…

Hi @Eran Roiter What have you tried thus far to solve the need? If you have a rule which is not working as expected, please post images of the complete rule, the audit log details, and explain what is not working as expected. Those will provide context for the community to offer better suggestions. If you have not started…

Using first with {{issue.fixVersions.first.releaseDate}} refers to an unknown ordering of the values in the field as it is undocumented. It might be the order the versions were added to the field, but if values have been added / removed over time, there is no guarantee of what it is. I recall there is a known, open defect…

Hi @Frederik Strøm Friborg -- Welcome to the Atlassian Community! Short answer: if you create your comment and transitionId variables with default values before any rule conditions, their values will likely be preserved after updates (replacements), allowing the use of a single web request action at the end of the rule.…

Hi @Frederik Strøm Friborg -- Welcome to the Atlassian Community! I have not seen any suggestions or updates on adding Lookup Tables to Data Center automation in over a year: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798#M966 Without those, long blocks of…

That will work for summing Subtasks up to their parent Story as the smart value {{issue.subtasks}} should contain all possible fields of the issues. It will not work for summing the Story values to the Epic: the REST API must be used to sum the time tracking fields for the update.

Certainly! To do that, please try the Log action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action I often start many rules like this to test-as-I-go: * trigger: scheduled (with or without JQL) * action: log some smart value expression With that, I can rapidly experiment to get the…

Yes, that is correct. That first rule takes the place of the bulk-loading suggested in the article by @Daniel Eads and would work for a smaller number of users (although requires manually entering values in the table).

Well done! Smart values are name, spacing, and case-sensitive, and frequently do not exactly match the field's display name on the issue pages. When an incorrect one is used, that returns as null. And even when the correct smart value is used, some are not supported and the custom field ID must be used in rules.

Hi @Darko Jozipovic Adding to John's suggestions... Sometimes custom fields added by marketplace apps can be accessed in rules using their custom field id, such as {{issue.customfield_12345}} rather than the smart value name. To learn if your field is supported by rules, please use this how-to…

Hi @Manali Butey -- Welcome to the Atlassian Community! As Jira Misc Custom Fields (JMCF) is a third-party addon / app, I recommend contacting the vendor through the marketplace for support on this question: https://marketplace.atlassian.com/apps/27136/jira-misc-custom-fields-jmcf?tab=overview&hosting=cloud Kind regards,…

Hi @Hizkeel Khan Adding to Stephen's suggestions... Those two relative sizing fields are from a design choice by Atlassian: * the "Story points" field is the original one, and is used for Company-managed projects * the "Story point estimate" field was added for some odd reason for use exclusively for Team-managed projects…

Hi @Rajiv Ranjan Adding to the suggestion from @Rilwan Ahmed ... Automation rules trigger after some event has happened. They cannot prevent the event from happening. And so a rule could not prevent the Capability from transitioning to "Done"...Instead it could only transition the issue back to another status, and perhaps…

Hi @Sahir Maharaj You posted this: Based on my understanding, copying only the nearest release from an epic to a story involves leveraging Jira Automation with smart values. The smart value you’re using looks correct, but it might require further refinement in your automation rule configuration. Please explain why you…

Hi @Rita Arellano Where did you find the syntax for that expression as there are several unsupported / incorrect things listed? As written, that cannot work. If your source was a bot / AI tool, I recommend no longer using it to answer automation syntax questions. {{issue.fixVersions.filter(version => version.released ==…

Hi @Kristján Geir Mathiesen My apologies I was not more clear in my original post! Here is more context to help... Once inside an iterator (e.g., {{#lookupIssues}} ... {{/}} ) only data from the lookup results and lower in scope is visible. And so the table is not visible. The lookup table approach works for a single…

Hi @Kristján Geir Mathiesen There are two parts to this one: the Slack user ID and the issue field listing. How many users do you have for Jira and Slack to map to one another? * When you have just a few, you could use a Lookup Table to map them, using the Jira user's account ID as the key and the Slack ID as the value.…

Hi @Delaney Bannon -- Welcome to the Atlassian Community! Is "Last Status Change" a custom field you have added and which is a date / time type field? If so, please try this: {{#if(now.toDateTimeAtStartOfDay.isBefore(issue.Last Status Change))}}Test{{/}} You will need to confirm the exact smart value (or custom field ID)…

Hi @Sabareesh Kumar M -- Welcome to the Atlassian Community! Adding to Trudy's suggestions... Even though I would not recommend converting time tracking to / from relative sizing measures (e.g., story points), the reason your inline math expression did not work is due to the value typing: integer versus decimal.…

Yes, that might do it. I seem to recall a rule cannot change / clear a read-only field without calling the REST API endpoint. That may have been fixed for the Automation for Jira user, but you changed the actor to a different user to solve a different problem with the transition. If your field is read-only, why is the rule…

Happy New Year, @Darryl Lee !! Yes, and...regarding that feature: other than the problem the Delay() function is only available for Premium and Enterprise license levels, I see it only valuable for a narrow set of usages: * to delay when expecting some external processing of known duration to conclude * to try to…