Is it going to be delivered anywhere soon? 

It is very confusing for our customers receiving batched e-mails as they become very confusing and too long. We need to be able to configure this feature ourself if it batches at all or at least be able to choose the timespan for batching.

thomas.wozniak, that improvement was JRASERVER-69305, implemented in Jira 8.3.0. However, it is still not possible to configure the email batching delay "on a per-project basis" as requested here in JRASERVER-68967.

@seec:

This is possible with Jira 8.5.1 (maybe somehing below this version dont know currently)

Values are 2m,5m,10m,30m,1h

My company has added batching, which has greatly reduced the email spam.  However, my project requires a quick reaction time to changes in tickets, both on my project and other projects my project depends upon, and 10 minutes is just too long to be responsive.  I would absolutely love the ability to customize the batch time to reduce it to 2 minutes, so that quick changes are collected together, but it is still emailed out promptly.

I think the current solution is good as a "default way of working".

Many of the wishes above can probably be solved by adding exceptions on a "project level", where you can set a shorter or longer time span for all users of specific projects.

If possible and if it doesn't have a negative impact on overall server performance, the idea of adding a more fine grained configuration level using personal profiles seem good. Preferable as an exception for "default" and "project" levels. I do however think that this is more of a "power user functionality". Most users aren't even aware they have personal profiles.

+1

Having configuration of batch timespan per project as part of your personal profile would be great. This way I could choose to have:

• no batching for projects of highest interest to me (timespan=0 minutes)
• short timespan for projects of medium interest (timespan=some minutes)
• long timespan for information (timespan=daily)
• very long timespan for projects of remote interest (timespan=weekly)

It would be even nicer if each user could configure the timespan for himself/herself, or per group/role. Some users, e.g., in an administrative role, may only want one update a day, others, like developers, may want to know directly when something changes.

The batching is a good feature. In my team it would be nice in order to avoid a bunch of emails during bulk updates, but we feel 10 minutes is too long and would like the possibility to decrease it to 1-2 minutes, since we wat the same time want faster communication with customers. 

My team would love to adjust the batching! Most would rather get a daily update than get an email 10-15 times a day.