Bill Sheboy Expert

Awesome; I am glad to learn that helped! The "trick" to make variables retain values for conditions and single-issue branching is to define them before the condition / branch, and then replace (i.e., shadow) them inside. This method does not work for branches which could be on more-than-one-issue. For example: * trigger:…

The create variable action is available for Jira Cloud and Data Center versions of automation: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-create-variableCreatevariable This action was added in August 2023 with version 9.0.0 - 9.0.1. Please check with your Jira…

Hi @Sofia Grunspan Do you only need the maximum value or do you need to know the specific field? If you only need the maximum value... One way to do this is to combine the date values to form a list, and then find the maximum value. For example: * action: create variable (This will create a comma-separated values list of…

Hi @Ademola Oladele -- Welcome to the Atlassian Community! Have you checked if the names of the sprint is where the dates are showing, and so one team's sprint names include the dates and the other does not? Kind regards, Bill

Hi @Matt Caruso -- Welcome to the Atlassian Community! Short answer: no. Within an iterator, no other data is visible. For your scenario, there are a few workarounds, and the simplest one may be to not use the lookup table. Assuming your lookup only contains those types, you could do this: *Completed this week:*…

First thing, I am using Jira Cloud and not Server / Data Center, and that is what you are apparently using. Please investigate your version and test accordingly. With that out of the way... When using the multiple events trigger as you show, the rule has less information available. Try using the specific triggers to gain…

Hi @Matt Lind -- Welcome to the Atlassian Community! Some issue link types are directional, and so the inwardIssue attribute will not include all of the issue links. If you only wanted the inward links, please try this: {{issue.issuelinks.inwardIssue.key}} If you only wanted the outward links, please try this:…

Hi @Vojtech Kalab -- Welcome to the Atlassian Community! In your rule after the REST API call to get the test results from Xray, please try writing this to the audit log: {{webResponse.body.data.getTestExecution.testRuns.results.status.name}} That may confirm if the message is (or is not) being interpreted in a manner that…

Hi @Alexey Are all of the tasks created at one time in a single rule? If so, you could still perform the linking in that rule using this approach: * As each issue is created, save a variable with its key. e.g., varBEKey, varDesignKey, varMOBKey * Then use branch on JQL to access the issues and add the links needed. As the…

Hi @Sanjay Dangi In addition to John's suggestions... There are two errors in your current rule in the Send Email action's content: in the triggering issue line, the URL and summary are instead referring to the Epic as they are missing the {{triggerIssue}} prefix. Consider changing that line to this: Triggering Issue:…

Hi @Christine Jarvis -- Welcome to the Atlassian Community! Adding an FYI to these suggestions... Although there is an automation rule service limit of 100 emails / 24 hours, there is also a 100 email for all total notifications by the site for Free licenses. That would not appear to be linked to inbound messages to create…

Hi @Tyler Tate -- Welcome to the Atlassian Community! Adding to the other suggestions... Rather than checking if the old label is present with the regular expression, why not just use the changelog entry to get the prior value, and always remove the label. If it is not present, it will not throw a rule error. Kind regards,…

Hi @Gurinder Summan There is likely nothing built into Jira Cloud which can create your report format and add it as a tab to the team information. Some alternatives are: * Using examples of your report, determine if it could be reproduced using a Jira Dashboard with gadgets and JQL filters * Investigate the Atlassian…

Hi @Brian Gauthier -- Welcome to the Atlassian Community! As others have noted, that is the incorrect syntax for a smart value condition as {{else}} is not valid. For this type of rule, I recommend using a Lookup Table to convert the values to the…

Thanks for that information. It does appear you will need to branch to the parent first, however...Given the limitations of rules, an if / else condition cannot be placed inside of a branch. One workaround for your scenario is to capture the parent field first, such as like this to compare the id of the selected value: *…

Hi @Elston, Jonathan For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Moises No, that is not possible from an automation rule at this time. Rules use the REST API and there is no public endpoint to get the Teams for a specific user. These are the ones available: https://developer.atlassian.com/platform/teams/rest/v1/api-group-teams-public-api/#api-group-teams-public-api Here is a…

Hi @František Špaček _MoroSystems_ By default, the components of a rule (i.e., actions, conditions, branches) use the data loaded at the time of the trigger firing. They do not automatically refresh as changes are made by the rule or any other updates (e.g., other rules, user entry, etc.). The Re-fetch Issue action does…

No problem as you explained what you needed quite well. The challenge is what I described earlier: unless the project permissions make it Public, this is not possible. Please see this post with a similar response from an Atlassian support engineer:…

Context is important for automation rules. And so the location within the rule may be preventing accessing the Story Points field data. Please post an image of your complete rule to show that context. If you are unable to do so, I recommend working with your Jira Site Admin to contact the Atlassian Support team for…

Hi @christopher.branaman Although automation rules with a single project-scope can create (or clone) issues into other projects, they cannot access or update issues in other projects. Instead the rule needs to be multiple-project or global-scope. Please work with your Jira Site Admin to change the scope of your rule to be…

It is unclear to me of that smart value always contains JSON or if it is plain text. If it is JSON and contains a list, it should be capable of iteration and list function usage. I recommend writing the smart value to the audit log, then experimenting by picking text within the result to use with the split() function.

Awesome; I am glad to learn that helped! Each approach has its benefits for searches / parsing, so they are good to keep in the toolkit: * The first one searches on the entire inline, iteration value, and then requires more parsing for structured result handling. And it supports dynamic searches for stuff outside of the…

First, please read my response above, noting these things: * When a sprint is created, it has no issues assigned yet * See the example rule I described for the trigger Sprint Completed, and compare that to your rule. If that does not help find the problem, please post the following for context: * an image of your complete…

Without seeing your entire rule for context, you could use a branch on JQL to access the issue. If that does not help, please post an image of your complete rule, and images of any relevant actions, to provide more context.

In general, most of the automation smart values apply when an issue is available to the rule. For an incoming webhook from Jira itself, it is possible to send the issue content. But your source for the webhook is different. Using some of the data you reference, you would likely need to use your source control / release…

The JPD team created a new date format to span a range of date values. To copy the created field value to your custom field, you will need to use advanced edit with JSON: * identify the custom field id for your Created Date field, using this how-to…

Hi @Kate Erickson -- Welcome to the Atlassian Community! With the built-in JQL features, you may find the issues which are marked as flagged (or which have been flagged in the past) but you cannot see the flag comment in the results. For workarounds you could try... There are likely marketplace addons for JQL which can…

Hi @Samantha Barnes That field appears not to be supported yet for filters, grouping, or calculations. When I tried to copy the value using a custom-formula field, I got this error message: Field "Created" is not supported yet A couple of workarounds would be: * to sort by the field (as you have done in that image) or * to…

Although you could create an automation rule, triggered on transitioning the issue to done, and then edit to change the parent to another issue, I do not understand... Why are these daily tasks associated to any epic at all? What value does that provide? If the issues were just daily tasks, not associated to an epic, no…