Great. I just upgraded to Jira 7.1.9 - which I assume is close to v3.2. I will upgrade to v3.2 when you let me know that it has been released. I will then be able to go into production with service desk - so am very much looking forward to this

@Simon Saunders

Should be fixed in the version 3.2 which should be released in the next few days.

Hi Patrick - how is this one going?

Wonderful

seems the same is happening with Novell Groupwise - anything that is forward as attachment does not create an attachment in Service Desk

Of course Simon, i voted.

I hope the issue will be fixed asap, eventually we will evaluate the product again then.

Hi Markus,
Is there any chance you can vote for the issue? It seems ridiculous to ask - but we are stuck in a rubbish scenario where we have bought the product but can't get anyone at Atlassian to assign the bug to a developer. I am wondering that perhaps if there were more votes that would make a difference.

I absolutely agree with Simon Saunders. We tested SD and quickly ran into this issue.

We would have bought this product if this problem dont exists....

Iam watching this JIRA-Case since it was created and the fact that no one is doing sthg and the issue is not assigned to anyone disqualify Service Desk for us.

Fact: Most enterprise businesses use Microsoft Exchange and Outlook.
Fact: Many helpdesk calls have emails attached to them (so helpdesk can see important information). For instance if a helpdesk user:
1) receives a bounce-back email they will forward that email as an attachment to the helpdesk to interpret the reason for the bounce back.
2) has received and email with attachments that are corrupted, then the Helpdesk User will forward the whole email to the Agent so they can perform a proper examination.
3) Other times the email may have suspicious attachments/links that need examination. In this scenario the User will forward to the Agent the email as an attachment.

Business case: If Atlassian want to crack the enterprise market then catering for Exchange & Outlook is critical.

This is an especially important bug to address, as no indication is given to either party that there has been a failure.

As a result the product is dangerous (because the helpdesk users will assume the message has been attached and urgent action is being taken - while the helpdesk Agent will, likely, have no idea there was an email attachment - and will not know to ask the user to supply it through some other means).

Finally and more important to Atlassian: If this feature doesn't work for the helpdesk - then its not going to work for Jira Core. In Jira Core its really important that this works as in many cases the workflow will relate to a creating value by creating a draft email for a supervisor to review. If you cannot attach an email then Jira Core will not be useful in an Enterprise environment