Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,552,580
Community Members
 
Community Events
184
Community Groups

Error with Auto-replies (Duplicate header ‘In-Reply-To')

Andrea Rose
Andrea Rose Nov 10, 2022

Does anybody have the same issue with auto-replies, see below? We raised a ticket with the JETI support, but have not received a solution yet. In the outgoing email log we can see this error and it's the same when you reply from an issue manually: Duplicate header ‘In-Reply-To'

"We have issues with auto-replies which seem to have appeared since the last update of JETI. When I set up a mail handler, one of the options in the last part, when creating a ticket, is to send an auto-reply to the sender. This is currently not working.

It does show as if it were sent in the ticket log, but doesn’t reach the sender. I does also not appear in our tenant log, so it looks like it’s not even sent out from Jira."

Answer
Watch
Like Be the first to like this
133 views

1 answer

1 accepted

0 votes
Answer accepted
Andrea Rose
Andrea Rose Nov 16, 2022

This issue was solved by updating to the latest version 9.3.2-GA.

Reply

Suggest an answer

Log in or Sign up to answer
Product apps
Apps & Integrations
TAGS
AUG Leaders

Atlassian Community Events

See all events