Outlook (new): Initial email request to Jira missing from the conversation thread

Question

Hi everyone,

We use Jira Service Management as our IT ticket system. Most requests arrive by email, and almost everyone here uses the new Outlook.

Some colleagues use conversation grouping and noticed that their original request email stays separate from the Jira confirmation and all subsequent replies. The rest of the conversation groups correctly, but missing that first email is a little frustrating.

I searched Google and this community and found two related discussions, although neither quite matches our case:

Conversation Grouping – Outlook Office 365: A user reports that Jira Automation emails lack In-Reply-To and References headers.
Outlook Conversation Grouping “Re” prefix not working: The author couldn’t get grouping to work by adding “Re” to the subject. One reply explains the role of In-Reply-To and References in email threading.

We use the standard JSM customer notification, not an automation email. Looking at our headers, the first Jira confirmation references Jira-generated IDs rather than the original request’s Message-ID. Jira also adds the issue key to the subject. That seems consistent with the original email staying separate while later messages group correctly.

I’ve already tested moving the issue key to the end of the subject—no luck. Removing it isn’t allowed by the notification template.

Is there a way to make the standard notification reference the original email, or another workaround to include that first message in the Outlook conversation?

I’ve read about Enterprise Mail Handler for Jira Cloud as a possible option, but it feels like overkill and is too expensive for this use case.

If this simply isn’t possible with the standard setup, that’s useful to know too. 🙂

Thanks for your help!

Simon

Abaho Katabarwa (Katabarwa Labs) · Accepted Answer

Hi @Frohnapfel, Simon, this is a known limitation rather than something misconfigured on your side.

Outlook groups messages into a conversation using its own headers (Thread-Topic and Thread-Index) together with the subject. The customer's original email is sent by Outlook with those headers, but the notifications Jira Service Management sends back (the "request received" confirmation and later updates) are new messages generated by Jira, and they don't carry Outlook's threading headers or reference the original message in a way Outlook uses. So Outlook starts a new conversation for the Jira emails, and the original stays in its own thread.

There is no setting in Jira Service Management Cloud that changes this today. Practical options:

* Point people to the request in the customer portal (or the "View request" link in any notification). That always shows the full history, including the original email, in one place.
* If threading matters a lot to your users, some Marketplace apps send request emails in a way that keeps replies in one thread. That's worth a look if the portal isn't an option for them.

Ismail Bin Ibrahim · Accepted Answer

Hi @Frohnapfel, Simon

What you're seeing is unfortunately a known limitation of the standard Jira Service Management email channel rather than an Outlook-specific issue.

When an email creates a JSM request, Jira generates a new notification email (the "request created" confirmation). That notification becomes the start of Jira's own email thread and uses Jira-generated message identifiers in the Message-ID, In-Reply-To, and References headers. It does not reference the original inbound customer's Message-ID.

As a result:

* The customer's original email remains a separate conversation.
* The JSM confirmation starts a new conversation thread.
* Subsequent Jira notifications and customer replies typically group correctly because they all reference Jira's generated message chain.

Adding or repositioning the issue key in the subject generally won't solve this because modern Outlook conversation threading relies heavily on message headers rather than subject matching alone.

Regards,

Ismail.