Currently, we have JEMH set up such that users that are included on an email, that are set up in JIRA, get added to a custom field ISSUE_USERS.
We would like the same to work for distribution lists that we have set up as groups in JIRA. So for example, if we had distribution list "User Group" <email@example.com>, set up in JIRA as group "User Group", and an email had "User Group" <firstname.lastname@example.org> on the cc, we would like JEMH to add "User Group" to an ISSUE_GROUPS custom field.
OK, so there are two points here,
Distrbiution lists (DL) are broken out into individual members when found. This is because a DL may have a JEMH inbound address as a member or may comprise of users who have JIRA accounts and should be added as watchers rather than just added to the custom field.
If you manually set a DL addressee as a custom field value, it will trigger a group notification to that address. as values aren't removed, only added, a situation would then occur whereby followups from the list recipients back to the list and JEMH inbox address, could result in both an inviduals email as well as the manually added DL entry, i.e. resulting in duplication notifications, possibly...
You could create 'another' cusotm field that JEMH did not update, that contained your ISSUE_GROUPS field that was manually managed, the JEMH Event Listener just needs to include it in the CSV list of fields that can contain addresses. But as the addresses are (currently) broken out, this would also result in duplicates.
Potentially, a way to make this work would be to have a specific DL processing option, whereby the DL was left unexpanded. This doesnt exist yet but if it were implemented, would require that you did not include JEMH incoming mailbox as a member, or a mail loop would result.
Is this what you think would solve your problem? If so, I can create an issue to get it implemented. New features are now feeding into JIRA 6.1+
Rereading this I think I have it -- you are suggesting that if I send an email to a unexpanded dl, JEMh could add that to the ISSUE_GROUPS, but if the JEMH incoming mailbox is in that group it will cause an infinite loop..
That would work for me.
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...
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!
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