Bill Sheboy Expert

Hi @Marc -Devoteam- FYI -- this can be done with one rule with Jira Cloud, but that is not a general solution... The solution is to first branch to the parent for the update (which gets substituted with inline code and avoids parallel processing), add a re-fetch (or delay) for a pause, and then use a JQL branch to update…

@Allah-asra, Yankal -- For the log you show, the branch found no child work items. Was that expected for that trigger work item? And...are the child work items in the same project as the Epic? When they are in different projects, the rule scope (in the details at the top) needs to change for the rule to access them. Your…

Regarding the spaces...without seeing your actual rule actions, I cannot guess on the cause. Even with the spaces inside of a math expression, those will be eliminated, as they were in my testing. And so the extra space is likely from one of the other rule actions. Finding "documentation" on the various smart value…

Hi @Randy O'Neal If the work item is valuable enough to keep when transitioning and setting the Resolution to "Won't Fix", why delete the Subtasks...as that is not reversible? What content do they contain? Perhaps also transitioning them would prevent the loss of information. Kind regards, Bill

Hi @Puneet Gupta Short answer: you may want to consider using forms or custom fields to constrain and manage input in specific layouts. Adding to the suggestions from @Marc -Devoteam- Although one could try to validate the format of the Summary, Description, etc. fields using text searches, regular expressions, etc., the…

Hi @Marc -Devoteam- FYI -- your link to that suggestion got truncated :^) Kind regards, Bill

Hi @Jen Bauer -- Welcome to the Atlassian Community! Please see the Atlassian response to that question in the original announcement: Changes to the API: In this release, we are not implementing any API changes related to the threaded comments feature. We will issue an RFC requesting feedback when we intend to extend the…

Hi @Mia Tamm _Simpleasyty_ I recommend pausing to review the community guidelines and those for app partners to learn if your posts violated the guidelines and were removed: * https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement *…

Hi @Sara Neither of the syntaxes you show are valid for smart values for date / time functions: * there is no built-in smart value to determine the number of days a work item has been in a specific status * please look here for the correct syntax to increment a date / time value: {{issue.someDateField.plusDays(123)}} For…

Hi @Flavien Gache Yes, that is possible, in several ways... * When you need just the keys for the work items, one could use the Lookup Work Items action twice: once to get the parent's data (i.e., the issuelinks), and then use another lookup with dynamically generated JQL for the action from that smart value. * When you…

Hi @__ Jimi Wikman First thing, I am not using assets, and thus my suggestions are based on what I know about rules in general. With that out of the way... My understanding is much of asset object data is looked up just-in-time as the rule proceeds. However, I wonder if there is "some" data still available in {{object}}…

Hi @Theresa Baumgartner -- Welcome to the Atlassian Community! There are several ways to solve this, depending upon what you are doing with the information... Let's say you and your team just want to review the counts together. That could be done with a Dashboard, selecting the project filter and using a gadget to…

Hi @Digvijay Singh Gehlot To ensure consistent behavior, I recommend solving this scenario with one single rule, and using the different field change smart values to detect what was added rather than using conditions. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange-- Using a…

Something is up...I just re-tested exactly what I posted above and it worked with no extra / embedded spacing. If you post images of each Create Variable action that will identify the cause. And just to confirm, you are using Jira Cloud, correct?

Hi @Mikael Sandberg FYI -- With automation rules, entity properties may also be accessed with the relevant smart value's object properties or rule actions. For example: {{issue.properties.myWorkItemProperty}} {{issue.assignee.properties.mySlackId}} Kind regards, Bill

If your variable is named CurrentDevCyle, you need the double-curly brackets around that in the JSON to be recognized as the smart value: { "fields": { "customfield_10627": { "value": "{{CurrentDevCycle}}" } } }

@Troy Anderson -- I was suggesting to change the JQL for the lookup action. The linkedIssues() function cannot be used inside of a smart value iterator as it is for JQL.

Thanks for that information, @Zaine Abaddin First, your variable is text, and needs to be split() back into a list for iteration. And...The symptom you are seeing is a long-standing limitation in the long-format of list iteration: Inside of a long-format iterator, only data from that scope, and lower is visible. Thus, the…

Thanks for those updates, @Dd Would you please show the details of your edit action, including the JSON expression? I hypothesize it "thinks" you are trying to use the field option id rather than the value attribute.

Hi @Akriti Sagar What is the source of the content you posted? As a reminder, when posting bot / AI-generated content, the source should be disclosed in the post's text. For more information, please see the Community Guidelines: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement Kind regards,…

Hi @Radka Svobodova Context is important for automation rule questions. Please post images of the following: * your entire rule in one single image for continuity * the action where you are trying to add the label * the audit log details showing the rule execution Until we see those... You describe getting errors for…

Hi @HaRsHaS' V First, the Jira version used impacts the automation options, and you have tagged your question with multiple versions. Which version of Jira are you using: * Cloud * Server * Data Center Next, does your upcoming version / release have any work items assigned to it in the Fix Versions field? * If yes...* Your…

Hi markus.neuwald@canon.at You are correct that the {{changelog}} smart value, when accurate, only contains information about the fields which changed for the specific rule's trigger. To do what you ask, a rule could: * use the Create Variable action to save the previous (or current values) * make the changes * re-fetch…

Hi @lukecalderone -- Welcome to the Atlassian Community! That seems to be the STATUS project in the JAC suggestion / defect backlog, although I do not see a suggestion for what you asked. Perhaps try adding it there:…

Hi @Des Kelly Yes, and...to the suggestions from @Mikael Sandberg The symptom you describe can happen with a team-managed project when: * there are team-managed project (TMP) and company-managed project (CMP) fields with the same name * and, one has accidentally added the wrong one to the view Kind regards, Bill

I wonder... For a given work item, can you write a JQL expression to return the correct work items, and use that to gather them with Lookup Work Items? Perhaps using the linkedIssues() function: project = SCR AND issue IN linkedIssues("{{triggerIssue.key}}", "is cloned by") ORDER BY key ASC ...adding whatever you need to…

One more thing...I recommend adding a "label" to the four rules when in the list (or name them in a way to associate them). This will help with maintenance, tracking problems, and to explain the rule set to other people. Happy rule writing!

Thanks for that information, @Allah-asra, Yankal Please post an image of the audit log details showing the rule execution. That will help identify why the update did not happen as expected.

Thanks for clarifying, @Michelle S For those fields, you will need three rules, triggered on: * work item updated (for Description or Acceptance Criteria) * work item transitioned * work item commented

Thanks for that information, @rpatrick In that case, I recommend adding the Re-fetch Work Item Data action immediately after that trigger (and before any other steps) to prevent timing problems. The reason is behind the scenes, the create definitely happens before the comment is added, leading to a short delay. Thus the…