Bill Sheboy Expert

Hi @Allanah Miller Which license levels will support this new dashboard / visualization feature: Free, Standard, Premium, or Enterprise? With the pending removal of some dashboard gadgets, knowing the supported levels of this new feature will help customers plan accordingly. Kind regards, Bill

Thanks for that information, @Csaba Vertessy Where are you viewing that result for the "Description" after the second API call? Does the markdown in that other system match the color syntax the Jira Description field is using: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=texteffects

That endpoint is to perform a bulk move as there is no "move one issue" endpoint (as far as I know). Thus, just pass one issue key to move it.

Hi @mark.liebold If you want to copy your custom field into the Original Estimate, shouldn't the Edit Issue action copy that custom field and not the Original Estimate back to itself? Also, there is only one issue in scope for this rule. Why does your custom field copy its own value back to itself in the edit? Finally,…

Hi @Rudy Holtkamp I would suggest trying smart value, list filtering or a regular expression with the match() function. The challenge for a scenario like this is finding the correct point to split the result message, if it is not interpreted already as a list. Have you checked the Tempo documentation or experimented to…

Hi @Bryan Henderson I respectfully suggest using a team discussion with your scrum master / agile coach and product owner / champion to align on: * what the group means by "defect", * how those are triaged, * how severity and priority work with defects, and * any definition of done criteria. That will clarify how to use…

Hi @Jamshaid How do you determine if an issue is a "duplicate"? Is the branch variable {{customCT}} used to set a value in the new issue so it can be checked for uniqueness? Please show an image for the Create Variable action of {{relatedCT}} to clarify the input values to the branch. Please show how you are are selecting…

Hi @dian_marsha -- Welcome to the Atlassian Community! For automation questions, it helps to include an image of the audit log details showing the rule execution. That will confirm which / how the steps processed. Would you please confirm if this is your scenario: GIVEN a Story exists with one or more linked Tasks with…

Hi @Catherine Ojok To which October update are you referring? I do not see any notes about sprint goal changes in the release blog information: https://confluence.atlassian.com/cloud/blog When I just tried showing the sprint goal for company-managed and team-managed project, scrum boards they worked as expected. Please…

Hi @Khira Niemeier To call a REST API endpoint from a Jira Automation rule, please use the Send Web Request action, as described in this article: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 Once you have the response message, you may parse that to…

Hi @Connor Skiro For this scenario, I believe you have a couple of options with built-in features: * Using the development triggers, save information needed with the impacted issues, including a date field. Using a scheduled trigger on JQL, evaluate any not-done issues where the dates meet your criteria, and then send the…

Hi @Patrick Cartier How have you tested that expression? What is in your lookup issues result? The way I would interpret that one would be: * for the results of the lookup as a set * return all of the sprint field's end date values* This will be a list of lists (issues and sprints), returning something like this (with the…

Your test dates shown in the create variable images are both for 2025. Please change them and re-test.

Sorry, I am not understanding the scenario. I thought you wanted to do this: GIVEN an issue in project ABC WHEN the issue's MY_FIELD changes to 12345 THEN move the issue to project XYZ That would make it the same issue, in a new project, and preserve the issue key referencing you described to John.

Isn't the last business day (i.e. Monday-Friday) of November 2025 the 28th, not the 27th? And so your test day should be the 26th. Rather than create issues in testing, I recommend using the list method I described and just writing both dates to the audit log. That will reduce cleanup after testing.

Hi @Dmytro Stasyuk _ SpecBright What is your relationship to the vendor of the product you are recommending? As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community…

Please post an image of your complete test rule, the action where the date change is happening, and the audit log details showing the rule execution. Thanks!

Thanks for that information, and I just tried this scenario on a team-managed project and got a similar result, with missing / incorrect values when the difference was negative. The positive diffs all worked for me, however... I found an open defect for this symptom: https://jira.atlassian.com/browse/AUTO-334 I tried to…

Hi @Sagar s gowda -- Welcome to the Atlassian Community! Short answer: you may need to call the Bitbucket REST API to get some of that information in the rule. The available PR-related triggers are PR Created, PR Declined, and PR Merged: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/ As those…

Hi @Bill Parlock For the person / user who performed the action that triggered the rule, please use the {{initiator}} smart value: https://confluence.atlassian.com/automation/jira-smart-values-users-993924862.html Kind regards, Bill

Hi @Elizabeth Basurto -- Welcome to the Atlassian Community! You rule is triggered and checks if the issue is a Task type, then branches to the parent (an Epic) and then tries to reference Subtasks of that Epic. That will not work, as Epics do not have Subtasks. And what do you mean by "average" in this context: the…

You can test almost anything in rules immediately, as follows: * action: create a variable with the date value to use, instead of {{now}}* name: varMyDate * smart value: 2026-10-05 * convert that to a date to use in your expression with toDate:* {{varMyDate.toDate}} * test your rule until it works as expected * edit your…

Hi @Rob Horan There is a REST API endpoint for bulk move, which could be used with the Send Web Request action to make the move (rather than use a clone): https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-move-post The user-dialog version of move goes…

Hi @Matthew Kijula -- Welcome to the Atlassian Community! That error is stating the problem: there are no issues to process because the trigger did not provide them. Normally the rule editor gives a warning for actions stating there are no issues available, but apparently that is not showing for conditions. When using the…

Awesome; I am glad to learn that helped! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Philip Kroos - TEAM XALT Context is important for automation rule questions, so without seeing your complete rule and where that expression is used, diagnosis is challenging. One thing is certain: please note you have nested the double-quotation marks in the expression, and so that is unlikely to evaluate correctly.…

Those two do not appear to be related as the text written to the log is not 99 characters long...unless you are embedding in within a JSON expression. Perhaps posting images your current, complete rule and an image of the audit log details for the rule execution will provide context. Until then... I recommend simplifying…

Greetings! Adding to Mark's suggestions, please review the documentation for the automation date / time functions to understand their behavior: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Kind regards, Bill

Import with a CSV file does fire the event and can trigger a rule with Issue Created. I hypothesize the challenge for your scenario is some data is updated after the issue is created (which is the same thing as when this happens in the UX). You will need to experiment to confirm if the issue history shows multiple events…

Hi @Robert J Thielen -- Welcome to the Atlassian Community! In the Jira Data Center documentation for the clone issue action, it states it tries to copy all fields it can, although it does not specify what "fields it can"…