I am using the mail handlers which is configured like this :
Strip Quotes: false Default Reporter: suggestion Bulk: forward Forward Email: xxxxxxxxxxxxxxxxxxxx Create Users: false Notify Users: false CC Assignee: false CC Watchers: false
My default reporter is 'suggestion'. But when Jira processes an address which is associated with an existing user, the reporter will be this user. How can I force the default reporter always be 'suggestion'.
It does, you can set a default reporter, and make that default override any other, so no user specific permissions are required in the project, whether they are JIRA users or not. JEMH solves the notificaiton issue as JIRA users can be automatically added as watchers, non-JIRA addressees can have their email address stored in a custom field, which is used by JEMH Issue Listener to issue notifications, filted, and customized as you like.
One way to do this is to prevent the users from accessing the JIRA project. JIRA only acts like you described it if the corresponding JIRA user (i.e. email sender) has the permissions to access the project. So to force JIRA to use "suggestion", you would have to prent all other potential senders to access the project.
Anyway, I am not sure if that is a sufficient solution at all for you...
Our workflow is a bit complicated...
Our customers can acces to Jira but they can't create issues (i know it's stupid...). To create issue they must send an email and then Jira create the issue.
That's why i want to force the user, because the customers can't create issues but the user 'suggestion' can...
now, why is it bad if the real username is listed? As they can not create issues everyone would know it's been done by email...
Anyway, another idea would be to forward the emails. So the user send the mail somae random imap and the mail gets automaticly forwarded to another imap which is where JIRA is listening at.
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