Bill Sheboy Expert

Hi @Justin Goodemoot The Work Item Created trigger (and others) have known, racetrack timing problems. That is, the rule can start running before all of the data is available for use. This creates symptoms such as empty fields, incorrect conditions, errors, etc. Atlassian knows about this defect and is working on…

Hi @Jade Tran What version of Jira are you using, as that impacts automation features: Cloud, Server, or Data Center? Until we know that... For Jira Cloud with the rule trigger Issue / Work Item Assigned, the changelog smart value contains the accountId of the previous user: {{#changelog.assignee}}{{from}}{{/}} But it does…

Hi @Josh Sherwood Thank you for that information, although I am still puzzled how what you describe aligns with common change management practices for an enterprise the size of Atlassian. For example, I recommend reverting the apparent batched changes to the JQL documentation as they were updated many months before the…

Hi @senne roovers What did you find when you searched for that? Did you find the REST API documentation describing this endpoint, and supporting information for using it: https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post Kind regards, Bill

Hi @Nikkita Willis -- Welcome to the Atlassian Community! I recommend reading all of the comments to those earlier announcement articles as customers note the many possible side-effects and potential problems that will likely happen because of this change. Specifically, I hypothesize we have not seen the end of the changes…

Hi @Anna Mjau Without seeing the details of your actual rule, a couple of things to try are: when the webhook has data referring to an issue... * branch to that issue, or use Lookup Issues with JQL, to get at the project information * use the Send Web Request action to call the REST API endpoint to get the versions' data…

Hi @Manav Shah Adding to the suggestions from @Mikael Sandberg ... If / Else Condition blocks cannot be used inside of branches, but branches can be used inside of If / Else blocks. Perhaps restructuring the rule will help, and... What problem is your rule trying to solve? That is, "why do this?" If you explain your…

Hi @Sameeksha Santhosh Naik Several things could cause that symptom, and the community will need more context to provide suggestions. Please post images of: * an image of the global audit log showing all the executions (e.g., since 1 October 2025) * the complete global automation usage information, particularly if you have…

Hi @Benedetta Russo What is the source of your information for your note below? This is likely due to a recent Jira Cloud automation change — lookups no longer expose child issue fields directly. There are no "child issue fields" described in how the original poster (OP) is using the Lookup Issues / Work Items action, and…

Well done, and that seems correct for what you describe! Please remember that will not do anything special for holidays / non-working days, so watch for that as you use the next Friday increment.

That is curious you can use JQL to select those work items with a value in "Ticket category" and it is not supported by rules. Where was that field created: a custom field, a marketplace app, something else? If you identify an example work item with a value in "Ticket category" and then use that how-to article to find the…

In that case, you would need to change the JQL in the trigger when needed and then enable the rule, run it, and then disable it. Unfortunately, the Manual Trigger for Data Center rules does not support User Inputs yet, and that would be a workaround. Another way to solve this is: consider when / why you need to run the…

I recommend doing a quick internet search for some basic HTML guides to get started. And, check for the email tools your recipients will use to ensure you do not use any table markup which is not supported. You may also review this example in a knowledgebase article to add an HTML table for a work item. The change for your…

Hi @Jeff P Do you need this one time? If so, you could create a Scheduled Trigger rule with a JQL expression to select your issues, run it one time, and then disable or delete the rule. Kind regards, Bill

Hi @Craig Duffy What have you tried to solve this? For example, if you have a smart value expression which does not work, please post that expression and what you observe happening. That will help the community offer better suggestions. Until we see that, have you tried using the date / time increment functions to do this?…

@Tom Cooper -- You have accepted the answers and describe there is still a problem. Is your rule working as expected? If not, please post images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks!

Hi @Erin Lee Yes, I did look at that again...the dynamic list-filtering approach is needed for several other problem scenarios I wanted to solve. However, it still does not work. (The reason is there is a defect with long-format, list iterators where many functions can only "see" the first record, and so filtering over the…

Hi @Tom Cooper -- Welcome to the Atlassian Community! Adding to the suggestion from @Jack Brickey ... The key is what event happens leading to creating the Jira work item? What does the person do first? Knowing that will help the community suggest if an automation rule can help, or of a marketplace app is required to help.…

Hi @Issac Franklin David -- Welcome to the Atlassian Community! Short answer: I do not believe that is possible with an automation rule when there is a lot of content. You may want to investigate the Atlassian Marketplace for apps to do this type of reporting. Rule actions, branches, etc. all have limits on the number of…

Hi @Sarah HaÏm-Lubczanski -- Welcome to the Atlassian Community! There is a template rule which is close to what you describe: Change page owner when scheduled for pages with deactivated accounts Unfortunately, the Change Page Owner action does not support entering a smart value, or selecting the option, for the page or…

Hi @igor_rivin -- Welcome to the Atlassian Community! Unfortunately, all possible fields are not shown in the dropdown lists in automation rule Create Work Item actions. I recommend two things to determine if your field can be set: * Use this how-to article and confirm if the field is supported by rules, and what its smart…

Hi @john.monteith Short answer: This symptom is caused by data typing, and possibly smart value naming, problems, and can be solved with a "helper variable" to make the get() work. Skip ahead to the end if you just want the answer without the "why". Why This Happens Your expression is running into documented and…

Hi @Santosh Racha -- Welcome to the Atlassian Community! Would you please add more details to what you are trying to accomplish? For example, are you trying to: * copy-and-paste text from the Description of one item to another, or * copy some fields with automation, or * something else? Kind regards, Bill

Using the built-in Jira, email handlers, if the responder does not alter the subject or earlier email body, adding a comment is possible: https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/ I have not used JSM much, and my understanding is it has similar email parsing to add…

Have you confirmed that token works with other endpoints (e.g., get a work item) by temporarily changing the action's URL and data, using the validate function in the action? If so, it may be time to ping Atlassian Support for suggestions.

Hi @Ann Mary Thomas (RBEI/ETB41) First, I have not tried that with a Forge app. After a quick search in the developer community, I found these related diagnostic steps to help get a board endpoint to work: https://community.developer.atlassian.com/t/error-using-the-get-all-boards-rest-api-on-forge/95779 Kind regards, Bill

Hi @Michael Schwienbacher As you found, when Jira Product Discovery (JPD) uses the "Delivery Ticket" feature, that is a special type of link. And the Story work items are in different projects than JPD, requiring: * the rule to have a global or multiple project scope, and * to have special handling due to the differences…

Was the API Token you are using created for a user with sufficient permissions to use that endpoint: Jira Admin or Site Admin?

For experimental endpoints, please add that additional header and re-test your rule.

Thank you, @Vinícius Pereira For other people wanting to track this symptom, here is a link to the public backlog item for it: https://jira.atlassian.com/browse/AUTO-2087