I’m working with Jira version 4.3.4 and need help with email configuration. I know that you can configure different outgoing email addresses for each project, which is really useful. However, I need to take this one step further.
I want to set up unique outgoing email addresses for individual components within a project. Here’s my situation: we run our customer support through a single Jira project, where each component represents a different client.
Each client has their own dedicated email like [email protected]. When customers send emails to these addresses, our mail processing system reformats the subject line to work with JEMH (Jira Email Handler). The system identifies the correct component based on the recipient address, which works perfectly for incoming mail.
What I’m trying to achieve: when a customer sends an email to [email protected], our system processes it and JEMH creates the issue. Then I want Jira to send notifications back to the customer using the same [email protected] address in the From field, not the default system address.
Is there a way to configure component-specific outgoing email addresses in Jira? The project-level setting isn’t granular enough for our needs.
Unfortunately, Jira 4.3.4 doesn’t support component-level email addresses - it only goes down to the project level like you found. But here are a few workarounds that might help.
Since you’re already using JEMH for incoming mail, check out its outbound features. JEMH has some advanced reply address handling that could work with your setup. You’d configure it to dynamically set the reply-to or from address based on the component field when sending notifications.
Another option is customizing your notification scheme with velocity templates. You can modify the email templates to pull the right sender address based on component values, though this needs some dev work.
Your third option is a post-function workflow that updates notification settings programmatically when issues are created or moved. This requires custom scripting but gives you the most control over email routing.
yeah, you’ll probably need a third-party plugin for this. Jira’s built-in email features weren’t built for component-level control back then. check out scriptrunner or similar tools - they let you hook into email events. I’ve seen custom setups where ppl used groovy scripts to catch outgoing emails and change headers on the fly based on issue fields.
Had the same issue with our multi-tenant setup a few years ago. Here’s what worked: I built a custom notification listener that catches emails before they go out. It checks the component field and swaps the From header to match your client addresses. You’ll need to do some Java dev, but it plugs right into Jira’s notification system. The plugin hooks into the mail queue and changes sender addresses based on component mappings you set up in a config file. Best part? Your existing notification schemes and templates keep working exactly the same - the address swap happens at the transport layer. Way more reliable than messing with templates since it catches every outbound email no matter what triggered it.