I have been searching everywhere on Google and Atlassian documentation/FAQ, etc...
Sometimes a colleague receive a question by email from external user. He forward to our email email@example.com, which is creating the ticket.
But the original sender is the colleague's email address.
When I close the issue, my colleague will get the notification. Not the external user.
Is there a way, when editing an issue, to also being able to edit the original sender's email address?
Is it done with a plug in? is it only a matter of configuration?
Thanks for your help
It's not really possible because Jira doesn't know what the senders email address is. Your colleague is getting the email because they are the one who raised the issue, not the external person.
To fix this, you need to capture the external email somehow, in the issue (not just as part of the description), and then find/write something that will send email to that email address alongside the usual notifications.
Thanks for your answer!
But on top of my ticket, it seems that the email address is registered somewhere.
The original sender is identified by his email, then we get his name, his company, country, etc.
The problem is that I cannot open a ticket for a client, then just modify the email address.
I have to tell the client : "please, resend your request to firstname.lastname@example.org , not to my personal email"
Which is confusing for the client and a duplicate...
I am not really the developer in our company.
In fact, I was asking here, hoping there was an easy solution, just in the configuration. Hoping many users of Jira were able to edit this. (It seems to be a setting just in our Jira...)
As you can see in the screenshot, our Jira is capturing somewhere the email address, then link it to a database of our users to find the name, country, organiation/company, etc.
Nevermind, thanks Nic for your time and answers.
I guess it's not an easy box to click somewhere.
I won't be able to put my hand in the code or the deep configuration things...
Too bad, I'll have to wait a new developer to be hired.
So it's been modified to capture the user mail, that's good. But you still need a plugin to enable "send to aribitrary and insecure email address based on the content of a custom field".
The reason it's insecure is that Jira sends email to users, which are entities with permissions to see issues (it won't send mail about an issue to people who can't see it). If you enable a send to an email address instead of a user, there's no view security, so it's possible to send priviliged information to someone who doesn't have permission to see it.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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