Bill Sheboy Expert

Hi @Ran Wronsky There are several ways to solve this... If you have any of the marketplace addons for JQL, you may be able to find the issue in one step, and then branch to the Request. If not, another way is to use Lookup Issues to find the Epic and then JQL to branch to its child issues. Assuming there are one or more…

Hmmm... Without seeing the full details of your description field's markup, I wonder if it contains some newline characters. The match() function does not handle those well. Let's try adding to the expression to remove those: {{issue.description.replace("\n"," ").match("([A-Z]+-\d+)").distinct}}

Hi @Bin Yes, I have seen the same behavior, and I have not found the isEmpty function to be useful due to this problem with handling null values as "empty". I recommend using other methods to detect an empty value. Kind regards, Bill

Hi @Amal_Hoetmer Adding to Walter's answer...there are several open suggestions to add that capability. Please watch or vote for these to see any progress: https://jira.atlassian.com/browse/JRACLOUD-59765 https://jira.atlassian.com/browse/JSWCLOUD-16051 https://jira.atlassian.com/browse/JSWCLOUD-23664 Kind regards, Bill

Hi @SAzaruddin.mp All of the things you describe seem possible with automation rules. This scenario seems quite specific to your needs, and I recommend you try the following: * First thing: do not work on this alone* Complicated solutions like this need to be understood by multiple team members * Partnering with others…

A smart value may be used in issue linking by typing in the smart value, and selecting it when it appears below the field. If your rule is able to extract the issue key, such as from a comment, it can be used as described above. Have you considered other approaches for this scenario? Perhaps issue import would be better if…

I do not understand your explanation. Do you mean: When I add a comment with attachments Then the attachments are not copied to another issue. If that is the case, the defect I noted is the problem. If it is something else, please work with your Jira Site Admin to submit a ticket to Atlassian for…

Hi @koutarou ishibashi When the rule is running, it is not possible to edit a created Lookup Table. The rule can only be edited when revising the rule. Several community members suggested dynamic updates / re-create of a Lookup Table in rules, as seen in this threads…

Hi @Vicky S -- Welcome to the Atlassian Community! First thing: this is a older thread, and so I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of people see it to offer help. When you create the new question: * describe the problem you are trying to solve: the…

Hi @Alejandro Moreno 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…

Thanks for that information. Please post an image of the details of the Create Issue action. And, did you note my comment about challenges with the Issue Created trigger, and how to address that?

Hi, Oday. The current text of the question states (emphasis added by me): "...will send an email exactly 7 days after the specified start date" Thanks, Bill

Yes, that is the one: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action It allows writing text, test values, etc. to the audit log for review after the rule runs. This will show what the smart value expression is parsing into before trying the comparison on it.

First, try writing that expression to the audit log before the condition: {{issue.description.match("([A-Z]+-\d+)").distinct}} And...perhaps change to use a smart value condition instead of a : * first value: {{issue.description.match("([A-Z]+-\d+)").distinct}} * condition: does not equal * second value: leave this empty

Hi @Tiago Chevalier -- Welcome to the Atlassian Community! There are several ways to solve this need: * Use the if / else conditions, testing for each status value to set the date * Use a lookup table, using keys for the status values and values for how much to adjust the date * Use separate rules, checking in the Issue…

Hi @Mark -- Welcome to the Atlassian Community! You can check that by adding to the JQL the scheduled trigger uses, such as with the now() or startOfDay() functions, and adding an increment, such as: project = yourProjectName AND "Start date" = startOfDay(7d) ORDER BY "Start date" ASC…

Thanks for that information, Rachel. When I try that match() expression it finds the issue key twice, due to the way the markup works. The fix for that is to add distinct to return one key per issue: {{issue.description.match("([A-Z]+-\d+)").distinct}} Please note: if there are multiple issue references in the Description,…

Hi @Rachel Godina The link issue action only takes one key, and so there could be challenges if: * there is no match * there are multiple matches * the match is to an issue key in another project (and the rule is project-scope) I recommend writing that match expression on the description to the audit log to observe what it…

Some things are the same and some are different for Jira Cloud versus Server versions of automation rules. I am using Jira Cloud and so cannot experiment directly with the expressions. Let's try breaking this down into pieces. To go faster, I recommend creating a separate, scheduled-trigger rule, with only the lookup and a…

That is possible: there is no documentation on what the rule engine does to present the content shown in the log. (e.g., removing control characters) Please use the how-to article I noted earlier for "Find the smart value for a field". With that... * you may call a REST API function to present the issue data as JSON in a…

Hi @Richard Lim Please post an image of the audit log details; that will provide the specifics of the error to help the community offer suggestions. Until we see that... The Issue Created trigger can fire so quickly that some data may not yet be available to the rule. This can cause unexpected rule behavior and errors. The…

Hi @Mutha, Poonam That appears to be related to "Enable ZIP support" being disabled, which seems to give an incorrect error message: https://jira.atlassian.com/browse/JRACLOUD-80321 Please check with your Jira site admin to learn if the setting is disabled:…

Thanks, @David at David Simpson Apps Perhaps posters of the artificially-written content are trying to rapidly add articles to win some type of community badge, or gain vendor visibility. (Increasing ploy I have observed: posting what appears to be a generated, informational article, outside of the app central area, and…

Hi @Damien Do you want to still send an email (perhaps with a different message body) when there are no issues, or send no email message? If you want to send no email message, try the condition suggested by Stephen and John. If you want a different message, you could use conditional logic within the email body to show…

Hi @Ste Wright With the bulk-handling feature of Server / Data Center rules, I believe the smart value is plural: {{issues}} And so the condition would be on: {{issues.size|0}} Thanks, and kind regards, Bill

Thanks for that information, and please see my first post for alternatives: marketplace addon or text-based chart created by an automation rule. Yet, I am still puzzled by what you are doing... You mention a burn chart, and so I assume your team is using Scrum practices. If using Scrum practices, why wouldn't the team…

What I suggested was based on what you showed, assuming it was from the plain text. It appears what you showed in the question does not reflect the plain text representation of the markup in the field. I suggest writing the field to the audit log by itself, run the rule, review the log, and that will clarify which…

Hi @Ahmad Sidawi 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 ideas.…

Hi @Alex Hall Adding to Mikael's suggestions: Here is the cloud version of the automation limits and packaging guidelines: * https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ * https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update A rule like this needs caution…

Hi Joshua, One way to do this is to create a variable to save the entire URL, perhaps named varUrl using the Create Variable action. Then write {{varUrl}} to the audit log to see it. The same variable may then be used as the URL for the Send Web Request action to confirm both are the same value. Kind regards, Bill