I think what @AlexKaras was saying about support was directed at JIRA Support. Since the generated files can be opened locally (and you can double check to make sure that the mht file size isnt 1kb, generally they are a few mb), it seems not improbably that this issue might be stemming from the JIRA side of things. In which case, I imagine that JIRA support has dealt with issues like this where attached files are not opening/getting corrupted/etc.
If you are seeing that the generated mht files are like 1kb, then please do make a support ticket and reach out 🙂
I think what @AlexKaras was saying about support was directed at JIRA Support.
Yes, correct. Sorry for not been clear enough.
I am seeing the the difference in file is 10 KB. The file attached in Jira is 746 KB. and the file which get exported to Hard disk is 757 KB,
> The file attached in Jira is 746 KB. and the file which get exported to Hard disk is 757 KB,
Personally I would double-check the code that attaches file to Jira (just to be personally OK with the implementation) and then talk to Jira admins.
P.S. If you attach exported log to some Jira entity and get the attached log back, is its size truncated as well?
Well, I see nothing special with the code...
My current guess is that it is some Jira issue. Or, maybe, something in-between (mail server?) that handles potentially unsafe mail attachment.
No idea but you may try... 🙂
Using Outlook as an example: Outlook (or Exchange?) blocks attached executables or executables packed into .zip archives. But executables with changed extension (for example, from .exe to .ex_) are transferred without any problem. (I understand that this most probably is not something that Jira users will like because .mht with changed extension will not be opened from Jira item and will require to be downloaded to local disk.)
Hi @nisgupta , have you managed to solve this? Please share your current progress with us!