Thing is, you say 'all headers', that can be a lot of stuff, the assumption is that you actually want specific headers like the usual addressee data?
Mapping incoming headers to custom fields on create sounds like something JEMH could do in the future without too much effort, its not been a case asked for previously. How did you envisage that working, just a great blob of text or stored one field per-header?
Can you answer the question, what do you actually want to do, capture all or route specific headers? Future for me probably means something different to your view ;)
My time horizon is measured in days. So immediate is much closer to right now.
What is needed is the ability to capture ALL of the email headers and put them in a singe multi-line custom field.
So, I want all of the received-from headers, all of the X-* headers, everything that is a header.
That is immediate not future! Well, either you have to write a mail handler from scratch to do that, in days, or be a little more patient! Implementing generic features like that in JEMH is something I do all the time, but I have priorities too.
What JIRA version are you currently on?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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