I think those designs look much better already as long as they don’t break, it looks like the good design once you get to solve the other issues being discussed in the docs
I actually find the repeating columns in the first design very confusing, the second one looks better to me and easier to follow. I think in most cases the number of attributes changing is quite low (usually one or two) so I don’t think it’s worth optimising for vertical space.
I also find Design 2 easier to read, even on a desktop size client. Design 1 seems like it needs an additional blank column in the middle, to visually separate the two sets of fields. (But either design is a huge improvement over the current plaintext layout that only works with a monotype font. Thanks!)
Would it be possible to move the “Changes (by <name>):” bullet list above the table in the template? That might address the concern about the table length on mobile, by moving the “what’s new” information to the top. (Am I correct that the table always includes all of the ticket’s fields, not just the fields that have been modified?)