+1 I agree it's worth splitting Jira notifications and creating new mailing list for them.
DMYTRO LIASKOVSKYI Software Engineering Manager Office: +380 322 424 642 x 57729 <tel:+380%20322%20424%20642;ext=57729> Cell: +380 97 341 1315 <tel:+380%2097%20341%201315> Email: [email protected] Lviv, Ukraine epam.com <http://www.epam.com/> CONFIDENTIALITY CAUTION AND DISCLAIMER This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies. On 3/7/19, 21:58, "Henry Saputra" <[email protected]> wrote: Hi All, Seem like dev@ list flooded with JIRA updates. I am proposing to move the notifications to new mailing list issues@ to help reduce the noise. Only JIRA updates will still send to dev@ would one new JIRA creation since it is important to know new issues being created. Please let me know what you guys think. Thanks, - Henry
