Bill Sheboy Expert

Hi @Purevdorj Nyamdorj First, are you trying to add values or replace all existing ones? If you are trying to add, please see this example for another multi-select user field: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Request-participants Next, are you trying to set a user from…

Hi @Radhika Singiri Is that for the Xray Test Management addon for Jira, or some other addon app? If so, I suggest contacting the vendor for support. Kind regards, Bill

Hi @Parveen Taj Rather than using Jira to adjust a team/process symptom, I suggest have a conversation with the team about why this is happening. There may be legitimate concerns/needs for this ability, and the team can discuss and address them. Otherwise using Jira features to block this could lead to unintended and…

Hi @Ohad Shalev -- Welcome to the Atlassian Community! At this time, there is no non-experimental REST API method to access that content, and so no way for rules to access it either. You may watch this thread in the developer community to learn when that…

Hi @Hans Versteegen -- Welcome to the Atlassian Community! Yes, and...to John's answer: here is the defect for that symptom, which you may watch/vote for to see progress. https://jira.atlassian.com/browse/JRACLOUD-80070 Kind regards, Bill

I am not aware of other solutions; a mentioned person is represented by their accountId and inside of Jira that is all the tool needs. When you want to do more, you need to get the remaining user information the way Jira would: by calling the REST API function.

I am not quite following, but let me try to understand...Do you mean you want the card color stripe to change based on the length of time in a column, similar to the days-in-column dots? If so, try using multiple card color queries, and order them from highest to lowest. For example Red: NOT status CHANGED AFTER -14d AND…

Hi @Shady Makar Yes, and...to Jack's answer: How often do you need to do this and for how many issues? When infrequently, you could export the issues to a spreadsheet and perform the comparison there. Kind regards, Bill

Just to clarify, are you saying your field edit changed the field from 100 to 200, and the log of the value instead shows 250.0? In that case, I suspect you have the wrong field's custom field id (or that it is a calculated field from an addon app and so may not be supported). Let's try this, based on this how-to article…

Hi @Ward Schwillens_ Schwillie What do you mean by "last issue comment scripted field"? And to which library of examples are you referring? If you are trying to use an automation rule to access this information, based upon the issue commented trigger, please look here for the smart values to…

Hi @Alexis Gutierrez You cannot color-code a swimlane (the horizontal ones), and...I wonder if instead you mean the columns for the status values. If so... What type of project are you using: company-managed (CMP) or team-managed (TMP)? For CMP, there is a feature for the Days-in-column which can be enabled to show how…

Short answer: no. That activity area is listing multiple things: comments added, the history (i.e. issue changelog), and work log (i.e. time entry for the issue) You can access the comments and work log entries from an issue in a rule. But the change log entries are created for each issue change, and so happen one at a…

I am unclear what you mean, as the Comments are shown in the Activity area: Do you mean in another field/region of the issue view, perhaps from an addon app?

Hi @Maksim Beliaev -- Welcome to the Atlassian Community! I do not know the answer why Atlassian went that way, and here is a suggestion to allow Project Admins to import rules...without help of a Site Admin. Please watch/vote for the issue to see progress. https://jira.atlassian.com/browse/JIRAAUTOSERVER-83 Kind regards,…

Hold on...You are pasting the value in the IF condition as JQL, when that was meant to be logged. That definitely will not work. If that was intentional, instead please trying using an advanced compare condition: * first value: {{#=}} {{varErrors.asNumber}} + {{varWarnings.asNumber}} {{/}} * condition: greater than *…

After the trigger in your rule, select Add Component, and then select the one for Log Action, such as below: Select Save, and do the same thing for the other two smart value entries. Then run your rule, observe the audit log details, and post an image of what you observe.

As I noted, you will need to call the REST API to do that... Here is a now-to article on calling the REST API from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 And the method you want to call is this…

Hi @Emil Moses -- Welcome to the Atlassian Community! That is not possible directly as the mention only contains the accountId value. You may confirm this by writing this value to the audit log in the rule to learn how mentions are implemented: {{issue.comments.last.body}} What problem are you trying to solve by doing…

The smart value for that field is fixVersion or "Fix versions". Smart values are name, spacing, and case-sensitive.

Hi @Naman Jain What have you tried thus far to solve this problem? If you have started an automation rule and it is not working as expected, please post images of the rule and audit log details; those will provide context for the community to offer suggestions. If you have not started your rule yet, please consider trying…

Hi @tomas_kadlec Do you mean from the drop-down list when selecting the value? If so, have you tried archiving values after they are released (on the Release page) so they are not shown in the list? Kind regards, Bill

Hi! To clarify what I described, automation rules execute when something happens (i.e. an event), such as issue create. And so the rule does not run until after the issue is created. When you click the "create" button to add a new issue, it does not exist until the issue is saved; that is when a rule can run. If you want…

Hi @Herve Wiederkehr What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. Thanks! From what you have described thus fare, what do you want to accomplish: * have a default value of the word "Project" when an issue is created * add the word "Project" to the beginning…

Thanks for that information, @Jocelyn Aquilina What is the type of your custom field: text, number, single-select, etc.? And, let's add some diagnostic checks to help see what is happening...After your trigger, please adding three writes to the audit log using Log Action containing each of these values. Then run the rule…

Hi @Sebastien Pierron For the log message which shows the error, what are you trying to write? Is it one of these: Warnings + Errors: {{#=}} {{varErrors}} + {{varWarnings}} {{/}} or Warnings + Errors: {{#=}} {{varErrors.asNumber}} + {{varWarnings.asNumber}} {{/}} Please note my earlier post had too many curly brackets at…

Hi @Barış Baysal Mostly, in a few ways...You can do is check if the status did not change DURING a window of time: project = myProjectName AND NOT status CHANGED DURING (date1, date2) You could also use the AFTER or BEFORE operators, if those would better match your needs. You may also use the relative date functions, such…

Yes, and... I recommend temporarily writing the Description to the audit log just before the variables are created. That will provide context in the audit log for each rule execution when observing the impact. Once everything is working, it can be removed. Another thing to consider: per the automation documentation, the…

Hi, Jocelyn. Would you please post an image of your complete rule, including the details of the smart value expression, and the image of the audit log showing all the steps from that rule run? That may provide more context to explain what is happening. Thanks!

Well done! You might be able to do that in one statement by splitting the first created variable before the replaces, rejoining, and then using distinct. But that would be harder to maintain/debug if something goes wonky. Regarding my "last sentence" suggestion...What I could not tell originally was: do you want each…

Hi @Benjamin Rosenek To back up a bit...the Lookup Issues action now supports all of the fields in issues which are supported by smart values in rules. There are exceptions of unsupported fields, and you may learn which fields in your issues have supported smart values with this how-to…