Bill Sheboy Expert

Hi @Walter Buggenhout Yes, and...when I noted that symptom last week (while also asking about the older, large banner), the answer was: https://community.atlassian.com/forums/Announcement-articles/Community-release-note-and-maintenance-notice-for-March-5-6-2025/bc-p/2981313#M6889 Kind regards, Bill

Hi @Olie Ryan-George The Jira Product Discovery (JPD) date fields are JSON represented as text. And, as with many of the JPD fields, they can only be set with advanced edit with JSON in rules. Putting those together, you could use the {{now}} smart value, formatted as jiraDate to set your field: { "fields": {…

Hi @Rees, Ian There are several fields named "Goal" or "Goals" in Jira, depending upon the product and project type. What type of product and project are you using with the field: a custom field you added, a Jira Product Discovery (JPD) field, an Atlas goal, etc.? Thus, they also may have different field types. And,…

Hi @Sateesh Dara Several of the characters in the character-class for the regular expression are reserved, and so they need to be escaped. You note the Description field contains a table in HTML. Are you certain it is HTML or is it the rich text, table markup for the field (using pipe characters)? Regardless, it is likely…

Hi @Dmitry Alabyan I agree with Walter's suggestion as the separate field may raise the visibility of the information and make it easier to manage. If you still want it all in the Description of the parent work item, the "fix" is to add a delimiter to the Description so it can be parsed. For example, let's assume the field…

First, I recommend reading the documentation for the match() function and linked information about regular expressions (regex). It will help to learn what the function supports and how to write regex to support it. You almost have it correct; please try this one: {{issue.description.split("\n").match("\|ABC.*\|(.*)\|")}}…

Hi @Fabian Bröscky Short answer: Out-of-the-box Jira Cloud does not support intermixing *all possible* features of the different board types. I recommend identifying what your team wants to help effectively manage value-delivery, decide which board type to use, select that one, and mitigate any gaps found, possibly with…

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!

Hi @Jonny That would require an extra step for this scenario to filter for the desired state first, storing the results in a created variable. For example: * action: create variable* name: varNotArchivedVersions * value: {{#lookupIssues}} {{#fixVersions}} {{#if(not(archived))}}{{name}},{{/}} {{/}} {{/}} * Now strip off the…

Thanks for the follow-up, Marc. I forgot that asNumber is not supported for the Data Center version...and so variables cannot be used as numbers with the inline syntax: only the longer format math expressions.

Hey, I just noticed this got posted as a App Central "discussion" rather than as a Jira "question". Would one of the community leaders / managers please move it? Thanks! Back to the question... I am using Cloud, not Data Center, and so I wonder if the default value operator with the pipe actually works for your version of…

Thanks, Nick. All the listed articles you note which include that smart value use one of the link-related triggers. Guess I will experiment to see what happens :^)

Hi @Marc Isikoff For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution * explain…

Hi @Nick Haller Is the {{destinationIssue}} smart value available in rules for other than the Issue Linked and Issue Link Deleted triggers? There is nothing in the documentation to indicate this or what the value represents in other contexts. Thanks, and kind regards, Bill

Hi @Michael Main -- Welcome to the Atlassian Community! Please see these related defects for that symptom, which appears to have started / worsened since the addition of the "new" external import and the sunset of several Epic fields to unify the parent / child relationships: *…

Rather than relying on the Sprint dropdown values in the Edit Issue action, you may need to set the value directly using the sprint ID from a smart value expression by using the REST API endpoints with the Send Web Request to either: * get the active sprint(s) for the board and use the ID value found, or... * use JQL to…

Hi @David Friedrich Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Akira Nakayama Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Sherri Queen Adding to Trudy's suggestions: The cloning-order behavior is a long-standing symptom, and there have been several suggestions to preserve the original "child" issue ordering. Most of them time-out and get closed after a few years, although here is an open one to vote for:…

Backing up a bit: the problem appears to be selecting the incorrect board for the sprint to be assigned in the Edit Issue action. You have multiple boards, and so multiple sprints. The correct board must be selected for the assignment to work as expected. This is validated by the test you did with the Lookup Issues action:…

Ah, the problem is the custom field type, and using the "id" attribute rather than "value" in that iterator because your values are IDs. I hypothesize if you made that change in the expression I provided it will work: { "update": { "customfield_10003": [ {{#varSystemOwners.split(",")}} { "add": { "id": "{{.}}" } }…

In your smart values condition, you reference the {{destinationIssue}} smart value, however that one is only available when using one of the issue linking triggers: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-linked I do not know that that value would even contain once inside of a…

What I meant is the "Resolved" field must have a value for the work items to display, regardless of the "Status" field value. Do your work items have a "Resolved" value? And has the several marketplace vendors responding have indicated, the built-in gadgets and reporting are quite limited in what they provide for…

Please show the following for context on what you have tried with you rule: * an image of your complete rule, in one continuous image * images of each: the trigger, and all conditions, actions, branches * an image of the audit log details showing the rule execution, with all of the areas at the right side expanded to show…

Hi @Monique vdB I am randomly seeing the "accept terms...or log out / cancel" pop-up in the community forum pages when I open multiple browser tabs to work through questions / posts...even though I accepted long ago. Is this a known symptom with the latest updates? Thanks!

Hi @stmiller Yes, and...to John's suggestions: When a team regularly starts unplanned work items after the sprint begins, that is a symptom of some root cause problem. That could include: * work items are not refined enough to be built, leading to pulling more work that is ready * the sprint plan is not aligned to team…

Hi @Sweer Huckels There are at least two open defects for automation rule conditions not functioning correctly for values in languages such as German: https://jira.atlassian.com/browse/AUTO-694 https://jira.atlassian.com/browse/JIRAAUTOSERVER-306 I recommend working with your Jira Site Admin to contact the Atlassian…

Hi @Martyn Sheriff I am curious: what problem are you trying to solve with this scenario implementation for that degree of sync between project work items? That is, "why do this?" Knowing that may help the community to offer other solution approaches. You appear to be on a Standard license level, and so the level of sync…

Hi @Rupert Ward -- Welcome to the Atlassian Community! Do you have any custom Work Item Types (formerly called Issue Types) in the project? If so, I wonder if it is related to this open defect for team-managed project types / field configurations: https://jira.atlassian.com/browse/JRACLOUD-93444 The workaround described…

Hi @Josh Sherwood FYI regarding changes for JQL -- It appears the documentation for JQL functions has already changed for things like linkedIssues() to linkedWorkItems() but the app does not support the new / aliased functions yet. This may lead to support requests.…