• 'Preview Unavailable' issue for in-line attachments in signatures

Over a year later and this is still impacting my team just sending an email from outlook OWA into JSM, so clearly isn't "fixed"

Thanks for the update @Manpreet! Are there any plans to roll this out to JSW and JWM?

Hi Everyone,
Thank you for your continued patience. I wanted to provide an update with respect to this feature request. I am happy to share that we have made some great improvements in HTML parsing. We have resolved the following bugs:

• 'Preview Unavailable' issue for in-line attachments in signatures
• Original table structure not maintained in single layer tables
• Ignore duplicates images in 'Attachments' section from email replies. This can also be tracked here: https://jira.atlassian.com/browse/JSDCLOUD-6037

 
I understand there are some other issues that continue to remain. To address them comprehensively, the plan is to track them separately and not on this ticket. Please vote for the respective tickets and make sure to watch the following issue for updates:

• Nested tables show distorted Jira view: https://jira.atlassian.com/browse/JSDCLOUD-8105
• In-line image distortion (images in email signature and email body): https://jira.atlassian.com/browse/JSDCLOUD-12462

 
Also, if you think there are other use cases that we have missed in our analysis, please reach out to me at msingh10@atlassian.com

Cheers!

Regards,

Manpreet Singh

I came up with some kind of "work-around" for this issue.

If you go to Settings > Products > Email requests > Hide email signatures in issues and portals
Then you can add custom text. I have collected most common email write-offs like "Kind regards" or "have a good day" and added them in that list.
It hides the signature as expected. 

However, adding every email write-off manually like this is annoying and time consuming. I hope Atlassian wil come up with a better "all in one" solution.

What is the latest on this one please; can we highlight and stress the urgency; This needs to be fixed within a few weeks, or we may have to look for another product that does this basic function.

Could we please get an update on the issue?

I have multiple colleagues that are having issues with "blown up" signatures. And it's annoying for me as well.
Having to scroll down to comment on a ticket takes to much time. Please put more people on this issue. Note that this issue was reported back in 2018!

Do we have news, preview of the solution for this topic?

at least add some delineation to orig email sent. ALLOW ONLY X MANY CHARACTERS? . once body of message is sent... cut the rest.  At least then the tkt would get created and if user wants to add pics etc.. or attachments they can go to the tkt to add

I've been asked by Atlassian support to add my comment here so that "[your] PMs and Developers can understand [my] scenario" 

I think it's problematically described in an existing ticket. The summary is excellent, but the Issue Type and Description aren't.  It's clearly a bug. 

https://jira.atlassian.com/browse/JSDCLOUD-2026

Based on the age of that ticket and it's relatively small number of votes, I have almost no hope it will be 1) seen as a bug at all and 2) prioritized for fixing, but here I go tilting at windmills. 

When you're parsing an inbound email, you seem to be mixing up "create" vs "comment" and running code for both.  There's no scenario in my mind, that a user would ever be creating AND commenting on a ticket at the same time.  Why an 'issue create' codepath should result in a comment is purely a mystery to me.  Perhaps it's some unhappy combination of JSM and core JIRA? (The tickets in question are being created via JSM).

Anyway, a brand new ticket with every image in the description, repeated in the first comment authored the reporter, is pointless. And a bug.  Please consider this in your bug round-up. 

Amen to brothers @Mohamed Patel and @Brandon Belanger

At the very least, strip off images in the email signature - please!

This issue is all the more pressing since we moved to the cloud.

Jira now not only adds the images embedded in the Requestor signature (as well as bona fide images embedded in the email body) as an attachment, but also adds a Comment with just the images, surrounded by huge blank spaces. So you now see the same useless images in 3 places:

1. Issue Description
2. Attachments
3. Comments

It soon becomes nigh impossible to find the attachment an email recipient refers to in an issue where there is a ping-pong email exchange! Atlassian is setting themselves up for WHS claims class action for RSI’s with all the death scrolling generated!