Bill Sheboy Expert

I am not currently using Assets with JSM and so cannot check that, although I expect it is possible. The challenge for your scenario is the volume of work items rather than where the values are stored.

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks! Regarding the user message in MS Teams, I do not know that answer. If there is a separate ID per user (as with Slack) you would need that user's ID to mention them.

Hi @Danno First, please post an image of your complete rule (in a single continuous image) for more context. Next, there are definite typos in that article you linked to, and so I recommend creating the dynamic JSON expression in a text editor to check / match up the syntax for bracketing. Finally, that error seems like an…

Hi @SianS For a one-time adjustment, the approach suggested by @Shawn Doyle - ReleaseTEAM seems a good one. For on-going removal of that prefix to cloned work items, you could use an automation rule to do this when work items are created. I only recommend this approach as you appear to be on a Premium license level and so…

Hi @Dd For a question like this, context is important. Please post the following to help the community offer better suggestions: * an image of your complete rule in a single, continuous image * images of any relevant trigger, actions, conditions, and branches * an image of the audit log details showing the rule execution…

Hi @Kris Dewachter Yes, and...for the suggestions from Marc: As the value is text, you could use the equals() function inside the conditional expression: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#equals-string- And, I have noted in some community posts there can be latency accessing…

Hi @Abhilash Reddy Sane -- Welcome to the Atlassian Community! The symptoms you describe indicate the rule is encountering one (or more) of the service limits: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ For the community to offer more guidance, and possible alternatives, please post the…

Hi @Trevor de Souza Please post an image of the second Edit Work Item Fields action for context. Thanks! Until we see those... This is not a timing problem; it is a storage / scoping one. When a Jira Cloud automation rule updates a field, such as with the Edit Work Item Fields action, it updates the data only in the Cloud.…

That is curious... I tried that earlier with a global / company-managed field for a Bulk Change from work item search and it found the field. Same thing with a team-managed project field. And, I just tried it from the backlog view's type of bulk change called "Edit Fields" and it also found the field. Just to confirm: Is…

Hi @Long Nguyen Xuan -- Welcome to the Atlassian Community! That appears to be a known problem: https://jira.atlassian.com/browse/JRASERVER-68793 There is a suggested workaround to change the default units for time tracking. Kind regards, Bill

Does that field have a date set in JPD? I recommend confirming that with a write to the audit log.

Hi @Frederik Rust -- Welcome to the Atlassian Community! First, there is a smart value attribute you may want to use instead of building the URL directly: {{triggerIssue.url}} Next, I believe you need to repeat the URL for this format: [{{triggerIssue.url}}|{{triggerIssue.url}}|smart-card] Kind regards, Bill

Hi @Steve Hooczko Where are you trying to perform the bulk change: from an work item search with JQL, or somewhere else? And, where is the field defined: in global settings, in a team-managed project configuration, in Jira Product Discovery (JPD), etc.? Kind regards, Bill

Please note my earlier comment about link direction, as that impacts which work item is the "trigger" and which is the "destination" for this rule trigger: Consider two work items: ABC-123 and ABC-456. When viewing ABC-123 and one adds a "is blocked by" link to ABC-456: * the {{triggerIssue}} is ABC-123 * the…

How are you updating the status of the work item such that it triggers the rule? When I tested with a manual status transition (i.e., direct field edit or drag-and-drop on the board) the status transition does not trigger Work Item Updated... However, with a drag-and-drop change on a non-empty board, the Rank field often…

Hi @Venkatesh Parthiban_G Please see the variations in the article I wrote for how to find the differences (or remove items) from one list based on another: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Find-Overlaps-Between-Lists/ba-p/3045704 If after you try that it still does not work,…

Hi @Ofir Oxenberg Noting my post earlier about integer-division for the inline math expression... When you want the decimal value for this case, switch back to the days units and use the long-format math expression: {{#=}}{{issue.customfield_10751.diff(issue.customfield_10750).days}} / 7{{/}} And if you want to manage the…

Hi @Anna "CoPandamonium" -- Welcome to the Atlassian Community! That could be done using an automation rule with a Work Item Linked trigger, and remembering to check the correct link direction. If your work items could be multiple projects, the rule will need a multiple-project or global scope, and you Jira Site Admin will…

Hi @Dmitry Alabyan When a work item transitions, that is a different event type than for an update, and so your rule with the Work Item Updated trigger should not run. Are you observing the rule run for a work item transition only, rather than bundled with other edits? If so, please post images of your complete rule and…

UPDATE: thanks, and it looks like we were posting at the same time :^) Please re-read what I posted above as it does not use the jsonStringToObject() function. Instead it uses this expression in the advanced branch as the smart value to generate a list of the non-empty lines in the Description field:…

Hi @Ofir Oxenberg If you write both of those date fields to the log before the condition, what do you observe in the values? Have you tried using the weeks unit of measure for the diff() rather than using days and dividing by 7:…

As a reminder: the Atlassian Community is a place for people with similar interests to learn and collaborate with another. It is not a free labor pool to provide turnkey solutions upon demand. A team's Jira Site Admin can help provide such solutions. Thus it helps to show rule and audit log images of what you have tried to…

The example Description you show is plain text, and not a JSON expression. Thus, there is no need to use any of the JSON functions. To iterate over any non-blank lines in the Description, please try this: * advanced branch:* smart value: {{issue.description.split("\n").match("(.++)")}} * variable name: varLine* In the…

Thank you for the additional information, and...Please stay within one thread when responding. That will help people reading this question in the future know if there are multiple solution approaches. As you want to update each work item daily, and you are constrained by the service limits of automation rules, you have a…

Hi @J D -- Welcome to the Atlassian Community! What does the content / structure of your Description field look like? And, why are you using the asJsonStringArray function? That is normally used to build a JSON expression as text to perform a work item update. That function does not produce a JSON expression which allows…

Hi @Sidharth verma How are you using the "warranty days" field? Another possibility is when you know the duration of the warranty period, add that amount to the value of {{now}} and store that in a custom field. Then a Scheduled trigger rule can use JQL to find work items for which the warrant period has expired to decide…

Are you still working on this automation rule? If so, please post images of the complete rule and audit log details, and explain what is not working as expected. If you have already solved this need, I recommend posting your solution as a separate answer and accepting it as "answered". This will help others in the…

Hi @Steven Dos Ramos -- Welcome to the Atlassian Community! As @Walter Buggenhout describes, although a board has a filter to manage which work items display, neither JQL nor automation "know" anything about boards. For rules, it is all about the data. To that point, one possible cause for the symptom you describe it a…

Thanks, and the next thing to check... How is the work item transitioned: by a person, by another rule, or some external app / process? * If person performs the transition from / to those exact status values, the rule should trigger * If another rule transitions the work item, the option "Check to allow other rule actions…

Based on that image, your rule is stored in a single project and so is not multiple project scope. That may explain why it is not triggering. Please show the rule details to confirm this.