HI,
> The problem seem to be coming from Jira side.
Yeah, looks like that... Maybe there is some Jira Support that can be asked?
Just as a side note: I would expect both files (initially exported to hard drive and obtained from Jira) to be binary equal. So that "fc /b <fullPathToInitialMHT> <fullPathToMHTfromJira>" to report 'no differences found'. If only a few bytes are reported to be different this might be the result of some Jira problem or the intended behavior of the browser that is used to access Jira. If files are too different... Well... I even don't have a good idea...
i am expecting support team should know how to figure out the issue becuase MHT report is generated by Testcomplete. They know the limitation of MHT report.
-Nishchal
StaffI 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 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,
Hi,
> 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?
