nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Eliminate Email Component Generated From Re-fetch Automation Step

Todd

We are using the Re-Fetch automation, and have to use that step three times to complete the calculation field in a report. the Re-Fetch option has an email component included within the automation.

Is there a way to remove or suppress the email's that are generated from this automation step.

Accepted answers

All comments

Bill Sheboy

Hi @Todd

Short answer: maybe.

For a question like this, please post images of your complete automation rule and the audit log details showing the execution. That will provide context for the community to offer suggestions. Thanks!

Without seeing your rule, I suspect you need to perform/store the results of any calculations (perhaps with the Created Variable action) and then make all the updates at once prior to a single Re-fetch action. Again, no knowing if that will help without seeing your rule.

Kind regards,
Bill

Jordyn K_ Lee

Hi @Bill Sheboy , I'm working with Todd on this.

re-fetch issue.png

The re-fetch component in the automation rules is really nice for interaction between fields in the given ticket to reduce load time. However, where as in every other component option email can be activated/deactivated, this one does not make this an option.

The automation runs so slow it is not worth having it at all if I can't use this re-fetch option. But I can't have people getting emailed for every single use of this rule.

Jordyn K_ Lee

calcrule#1.png calcrule#2.png

Bill Sheboy

Hi @Jordyn K_ Lee

Just to confirm...are the email notifications being sent due to the field edits or are they being sent by something happening later in the rule? You are not showing the complete rule so I am unable to determine that.

Also, seeing the complete rule may explain the slowness you describe. A re-fetch seems to take one or more seconds (in my experience). It is possible this rule is triggering itself, as the timing of the edits/re-fetches could cause that. One way to prevent that processing is to add a user condition immediately after the trigger:

user: User who triggered the event
check to perform: is not
criteria: Automation for Jira

This will halt the rule if it triggered from a rule initiated edit.

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud