You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Guys,
We currently have several projects in Jira Service Desk.
The problem here is that mails from, for example, new customers do not appear as tickets. You can see them in the email log at
https://XXX.atlassian.net/jira/servicedesk/projects/XXX/settings/email
is there a way to automatically forward a notification or this e-mail to another e-mail without discarding it?
We use Atlassian's email addresses and the cloud variant.
xxx@xxx.atlassian.net
Hi @Stefan
from what I understand the problem is addressed and improvements are on its way:
Please, in any case, open the link and double check if the finding corresponds with what you are seeing. If so, you could click on "Start watching this issue" to get further update regarding its progress.
Please let us know here if this was understood in a wrong way so Community members have a chance to follow-up.
Regards,
Daniel
The problem is that the mails come from different mail addresses. Because we do not have the service desk portals public, invitations must be created or the domains added.
The problem is that Atlassian discards the message if it cannot assign the evening
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What does the failed message say in the email log? Why are the emails not resulting in tickets?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.