Bill Sheboy Expert

Hi @Uliana Komiakovych -- Welcome to the Atlassian Community! Automation rules run after some event has happened. They cannot prevent something from happening. And...it is not possible to require the comment when flagging an issue / work item. Here is the suggestion to add that feature, which you may watch / vote for to…

Hi @Peter -- Welcome to the Atlassian Community! Do you mean the embed option does not show / work or that the links do not work at all? If it is the first one, please see this defect / suggestion, including the workaround noted: https://jira.atlassian.com/browse/CONFCLOUD-73899 Kind regards, Bill

That is great news! Now that we have the {{varAddedTags}} smart value with a list of Tags, such as: A, B, C You may use the Advanced Compare Condition to test if it contains one of the values needed. This would replace the Issue Fields Condition you used earlier. * Advanced Compare Condition:* first value: {{varAddedTags}}…

Hi @Sami -- Welcome to the Atlassian Community! First, you posted this in the App Central group, but it seems to be a Jira product question. Hopefully one of the community managers will move it. Next, for a question like this, context is important for the community to help. Please post the following: * what version of Jira…

Hi @Heather Ronnebeck If both your Team and the specific version number you show in the examples are unknown until the rule runs, the REST API will be needed to find the versions. The rule could use the Send Web Request action to call the endpoint to search for the matching versions by their name, status, etc., parse them…

Hi @Diego Marques Oliveira -- Welcome to the Atlassian Community! This is a very old thread, and so I recommend always adding a new question and including a link back to older threads for context. That will ensure the maximum number of people see your question to offer ideas. To save you some time: what you ask is not…

Thanks for the follow-up, Erica! I had forgotten about that defect, and... That response from the support team is very troubling, and they should change the defect Summary and raise the Severity of impact. Many rule writers likely assume the defect only happens for the Multiple Issue Event trigger or the Field Value…

In your rule's Edit Issue action, the smart value is in the field for Labels to Remove. Please clear that and put it in the Labels to Add field. And then re-test. If that does not help...please post images of: * the Create Variable action * the updated Edit Issue action * the audit log details showing the rule execution,…

Let's pause to confirm your scenario: do you want to send emails only for the added Tags? In that case, the rule can only be done if you have the Create Variable action in your Server / Data Center version (or with Jira Cloud). Do you have that in your version of automation rules? If so, let's first create a test rule,…

Hi @Rebekka Heilmann _viadee_ Would you please post images of your complete rule and the audit log details showing the rule execution? Those may help provide some context for the symptom you are seeing. When I tried that same ADF expression with v3 Edit Issue endpoint, it worked for me with the Send Web Request action from…

I believe when the text is passed in the advanced edit it will be parsed into JSON before it is validated. Did you try writing the expression to the audit log, and then perhaps copy-and-pasting the result into a text editor to learn if it is valid JSON? Also, when you need to convert text to JSON for other uses, the…

Would you please post images of: * your complete current rule, including the details at the top showing the scope, and * the audit log showing the rule execution with all the areas at the right arrows > expanded? Those may provide more context for why the field is not found. Thanks!

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

Yes, that is an addon. Please check that vendor's marketplace page to find their documentation, or support contact, to learn what is possible with the gadget.

Hi @Goran Dermeta There are several defects and suggestions around the sorting in those fields, with some of them over a decade old, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42225 My understanding of the current behavior (although I have not tested it recently) is to show: * unreleased versions (which…

Yes, it is likely a "smart link" and thus the email address is probably appears twice in the Description field's markup. For example: [emailAddress|emailAddress] You can verify this by first saving that extracted value to a Created Variable and then writing it to the audit log before using it in the Send Email Action. Once…

Please look in the address bar of your browser and you will find the ID as you select each issue / work item type.

Hi @Paul Pasler _Seibert_ As you are trying to set the field with advanced edit with JSON, please try adding the function jsonEncode() to the end: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonEncode-- This may require some fine-tuning, so I recommend saving the entire update…

Hi @Calvin Yes, with the built-in features of automation rules only a link to the attachment may be sent. Here is a suggestion to add the ability to include the attachments: https://jira.atlassian.com/browse/AUTO-1586 FYI -- The original suggestions for this feature have been open since before CodeBarrel's automation…

Hi @Anja Beyerbach Yours is the second community post I have seen in the last 12 hours for this symptom. I checked and did not find an open defect for it in the public backlog, so I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact/#/…

Hi @Kauana Rodrigues dos Santos I hypothesize your rule looks something like this: * trigger: scheduled with JQL to find the issues * action: send Slack message That will iterate over each issue found by the JQL from the trigger. One way to send one message with all the issues is using the Lookup Issues…

Hi @Sasmita Dash -- Welcome to the Atlassian Community! Short answer: Scenarios to clone multiple issue type levels (and links) rarely work as expected with automation rules. When one regularly needs such complicated cloning, investigate marketplace apps to help. There are many community posts describing partial solutions…

Hi @jeff_trotman If your custom field is indeed a "User Property Field" type, that is an entity property of a user. Please use the Set Entity Property action, selecting the correct type, user, and property name to set the…

Hi @Matthew Martin Yes, and... to the suggestions from David: Here are the open suggestions for Jira Cloud and Server / Data Center to add public REST API endpoints for rule management, which you may watch / vote for to see progress. https://jira.atlassian.com/browse/AUTO-51…

Hi @jira_admin_cu Are you trying to send one email with all of the issues to a group of recipients, or send one email for each issue to the same group? Send one email with all the issues -- Use a rule with a scheduled trigger to identify the issues, selecting the option to bulk-process the issues using the plural…

Hi @Devon Engen -- Welcome to the Atlassian Community! It is possible to do this with one or two rules. With one rule using the Multiple Issue Event trigger, select both issue created and updated. Normally, I do not recommend using this multiple event trigger, however for this scenario having one rule will reduce the…

In that case, please check the Tempo API documentation to learn if there is something missing in the message. Perhaps also try running the call from outside of the rule, with a tool such as Postman, to fault isolate if the cause is the message or the rule calling the endpoint.

Hi @David Tieman I recall there is some additional filtering on the "Recent rule run" feed where it does not show rules where "No Actions Performed" happened. Did the run you expected to see perform any actions on the issue? There is also a defect where single-project scope rules acting on issues in other projects (e.g.,…

Hi @Valerie Knapp Thanks for your article. A couple of suggestions for this scenario are: * The Issue Created trigger can have racetrack errors where all of the data may not yet be available when the rule starts. And this could cause problems using the fields to find the dates. The workaround is to always add the Re-fetch…

Hi @Susan Waldrip Your rule is using a JQL condition and using the smart values that way will not produce valid JQL. Instead please try a Smart Values Condition: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#--smart-values---condition Kind regards, Bill