We 1st ran into this issue in zd ticket #13579. As a summary, the issue (#612003) had suffered some glitch during the process of resolving it which caused it to glitch out when attempting to save it as Resolved even though in the database it already had the ResolutionDate filled out. We had to do a data fix to change the StatusTypeCode to RESOLVED.
We later found out that the issue was still causing the system to crash. After further testing, we found out the crashes only happened after accessing the Issue Log tab. Once there, if you clicked on any other tab, it would crash. Everything looked fine in the Resolution section, Resolution textbox, at first. However, when highlighting the text in the box we noticed that the version number (2.9.2.4534) appeared far off to the end of the textbox.
When we looked in the PROD database, we didn't see any formatting issues like we first suspected either in the Issue, OMBIssue, or the LogEntry tables. Just to be safe, we removed the extra spacing between the end of the resolution message & the phantom version number from the LogEntry table (as the resolution doesn't show up as part of Issue or OMBIssue). This change didn't change the behavior. It was then that we thought to look at the corresponding entry in the LogEntryFile table. Here we found all sorts of HTML formatting. We updated it to look like the LogEntry entry & this fixed it so it no longer crashed when switching off the Log tab.
0 Comments