Hi Atlassian, 

Can someone please update by when we can have this implemented as this is getting necessary as we expand the reach of JSM within our organisation.

We encountered a major concern because of this, there was an email with external participants and that created a ticket meanwhile one of the internal stakeholder removed the client and sent an internal note via email and that got sent to the client as a comment since they were added as a request participants because of the initial thread.  This created a serious concern within our organization and would love to see how these can be avoided one approach would be using smart values but not sure by when this will be implemented. Can you guys please suggest a workaround or otherwise we might have to look for other tools which are capable of handling these scenarios.

Please guide us over here and if there is any disconnect I would love to jump on a call and see how we can add a solution for this. 

Thanks,

Nishant

I actually really need this right now as a global ITSM manager.

Another use case for accessing header elements: recognize who forwarded original email. Our service desk flow contains in-the-middle email accounts which forward original emails. JSM creates an issues correctly on behalf of original senders, however, as an admin I would need in automation to recognize which account forwarded this email to make some additional tweaks.