Delays in notification scheme triggers Edited


Currently, the notification scheme is triggering correctly but it is triggering changes on every single change and not aggregating changes within a two minute block. 

Is there a setting to set delays in Jira to allow for less emails to be automatically sent and more changes aggregated into the email sent?



2 answers

0 votes

Could you explain how you have got Jira to aggregate?

So when I'm talking about aggregation of changes, I'm referring to a large amount of changes made on one save.


What I'm asking here is whether you can set a delay for the trigger so it aggregates multiple save information in a short space of time... like a 2 minute block rather than on every saved change.

I understand what you're looking for and why.

What I am asking is for the details of how you have set this aggregation up, because I can't talk to you about settings you've done and I can't see.

Just say for the default notification scheme's.

I haven't got custom setups for the aggregation of changes.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,820 views 18 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you