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.
Hello,
I have an email that forwards all emails into JSD. I noticed that when it arrives into JSD it adds the email account that forwarded the email as a 'Request Participant'
How does it do that?
This thread is still a popular result for "Jira forwarding address is added as request participant," and I contacted support about this today. I completely forgot how I'd solved the problem in the past, and they were helpful.
When Jira finds the forwarding address in the "To:" field of a new email, it automatically creates a customer/portal account for the address and adds the new customer to Request Participants. The way to fix it is deceptively simple: if you revoke a customer's access to the portal, they can't be a request participant anymore!
So, do the following:
Hello!
Unfortunately, this did not quite work out for me. The account is revoked however it still got added as a Request Participant and received email notifications. Am I missing a step?
Thank you
Natasha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm having this problem also. It's very annoying. Is there a way to turn this off?
Thanks
Rich
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.
We are actually having the same problem but it just recently started happening. Did you ever figure out a solution to this?
Thanks,
Jenny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The from address is considered to be the Customer/reporter so if the email is not already in the system it will be added. Unless you have the project setup such that only customers your agents add to the project. In that case an unexpected email would be rejected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks the reply.
Yeah I am ware of that. my question was around why the email account that is doing the forwarding is being added a 'Request Participant' and not referring to the 'Reporter' as you mention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it possible that the email address is also in the CC list? If not possibly some automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Harry Bob Did you ever get this sorted? Facing the same error on cloud and can not seem to get rid of the forwarding address set as request participant. Could always try automations to remove it I guess.
Thx 😊
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.