Bill Sheboy Expert

Hi @Amanda Crawford -- Welcome to the Atlassian Community! Please try adding the ORDER BY keywords to the JQL for your Lookup Issues action, selecting the order you want. For example: project = myProject ORDER BY Key ASC When there is no ORDER BY on a JQL expression, I would hypothesize the returned issue order to be…

Thanks for that additional information. I do not believe those things are possible with the built-in features. You may want to investigate the Atlassian marketplace to learn if there are addons which may help...although as the REST API does not support changing sections it still may not be possible.

Awesome; I am glad to learn that helped, Jennifer. And thank you, Hermance. Glad to try to help :^)

Awesome; I am glad to learn it is working now!

Once you are logged in, there should be hyperlinks to vote for or watch the issue at the top-right of the page.

I notice your rule uses the Issue Created trigger. That trigger can fire so quickly that the issue data is not yet available to the rest of the rule step. This can cause problems, such as apparently empty fields. I recommend adding the Re-fetch Issue action immediately after the trigger. That will slow down the rule a bit,…

Hi @van den Bergh, Marius, Vodacom (External) This appears to be a duplicate of your earlier question, possibly caused by the connectivity issue you noted: https://community.atlassian.com/t5/Jira-questions/Automation-Branch-not-editing-lookupIssues-but-triggerIssue/qaq-p/2706942 Kind regards, Bill

Hi @William Linder It appears you are trying to compare the human-readable field (e.g. containing values such as "3h") as a number and so the comparisons do not work as they are text comparisons. Perhaps try the numeric field for such comparisons: {{issue.timetracking.remainingEstimateSeconds}} And divide by the…

Hi @Alberto Torrejón 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 @Lucas Monteiro -- Welcome to the Atlassian Community! What is the trigger for your rule? The smart value {{pullRequest}} is only available with the PR-related triggers: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--Pull-request-- Kind regards, Bill

Hi @Lusine Yes, that is possible with a non-trivial automation rule. The rule would call the REST API functions to load the attachment data, iterate over it, and create the subtasks. If you want to try this, here are some references to get started: *…

Hi @Pavel Helia -- Welcome to the Atlassian Community! I am glad to learn you found an expression that works for you. As you discovered in automation rules, sometimes nested lists get implicitly converted to arrays...which then totally breaks use in many functions and iterators. Another example of this is the Sprint field…

Hi @Päivi Passila -- Welcome to the Atlassian Community! Many of the newer features of the releases pages have neither direct links nor REST API functions to access / update them: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-get What problem are you…

Hi @Christa Wyler The changelog and fieldchange smart values only have values when a field has changed and triggered the rule. Rule triggers which do not detect field changes will not work. And...some field changes do not appear (or appear incorrectly) in those smart values. For example, some list fields like Sprint and…

Hi @Jennifer Chang -- Welcome to the Atlassian Community! You appear to be sending the Slack message with an automation rule. Is that correct? As you have observed, JPD is using its own type of date field, which is actually text to represent a range of date values. For example: {"start":"2023-10-31","end":"2023-10-31"} And…

Solving problems with automation often requires understanding the context of the rule actions. Please answer / post the following to clarify the rule context: (1) What version of Jira are you using: Jira Cloud, Server, or Data Center? (2) If using Jira Cloud, what type of project is this: team-managed or company-managed?…

Yes, it appears that was the problem: looping over the data and not the issues. If does not appear you need the Lookup Issues action. Why did you use that? Please change the JQL branch to use the JQL directly from the lookup and not the lookup results.

Hi @Allam Castillo No, not with a variable as the Create Variable action stores text values. Some possible work-arounds are: * Instead of Create Variable, use Create Lookup Table as it can store object data. For example, if you store your object in the value for a row with a key of myIssue, the attributes could be accessed…

Hi @van den Bergh, Marius, Vodacom (External) 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…

Is your split(" ") as you just posted, or with the period in the email address: split(".")? Please post images of your complete rule and of the audit log details showing the rule execution. Those may provide context to help explain what you are observing.

Hi @Del_Singh1 -- Welcome to the Atlassian Community! For Jira Cloud automation rules, the "advanced compare condition" was renamed to "smart values condition". Kind regards, Bill

For scheduled trigger rules, you may run them immediately when you need to test them: just look under the ... menu at the top-right to run the rule. Of course if that will cause problems due the issue edits, please wait for the schedule.

For the first one, they will not necessarily compare correctly unless put into a known format. For example you could also compare: {{issue.cf_[22222].jiraDate}} less than {{now.plusDays(2).jiraDate}} That would but both in the format "YYYY-MM-dd", allowing the less than to work as expected. I recommend using the second one…

Let's try this: write just that custom field to the audit log to confirm what it contains: {{issue.customfield_10132}} Once we know that we can adjust the smart value expression.

Hi @mateus.oliveira I do not believe that comparison is possible with the built-in features of JQL. However if your rule used other criteria to find the issues first, rule conditions could be used. For example: * trigger the rule on issue created * use the date / time diff() function with units of business days to compare…

Hi @Dee Minty This technique works for text smart values. If your field is text, this may work: {{issue.personal email.split(".").get(0)}} If not, are you certain you have the correct smart value for your field? Smart values are name, spacing, and case-sensitive, and do not always exactly match the displayed field name on…

Glad to help! If you mean the second workaround, with the dummy issue for versions, I recommend adding a rule to automatically add the issue when versions are created in the SEAP project. That will help ensure they are present when you need them. :^)

Hi @Josh Allen Finding that information for the other project is not straightforward. To get the versions in the other project, I believe the rule would need to: * use the Send Web Request action to call the REST API to query for status=unreleased versions in the other project * find the earliest release date in the…

To limit the scope of your testing, I recommend first changing the scheduled trigger to only process a single issue. (Or add a condition to test for only one issue key.) Those can be undone after the rule works. Next, write both of the date values to the audit log before the diff() to confirm they contain what you expect.…

As for "when", the article notes the date of 17 June 2024. I recommend reading the update blog weekly and watching for the changes in green font noting "NEW THIS WEEK": https://confluence.atlassian.com/cloud/blog The article notes some specific date and date / time formats which may be searched for in rules. Also search…