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'.
Thanks
Interesting usecase. Not sure, but you should check Andy's JEMH. It will mostly support this.
https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
Thanks, but unfortunately it's not a sufficient solution for us :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's what I guessed. why do you need the reporter to be set to suggestion? There might be another way to achieve what you're looking for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.