That's a lot of extra stuff to read through. Do you summarise the discussion too?
Most places that I've been at that have worked this way have had periodic "checkpoints" in the tracker (usually when the code involved is sent to QA), where the current state is summarized at a 10,000 ft level.
In practice, these records are only read from beginning to end when someone new to the issue at hand needs to come up to speed. Otherwise, the value is in being able to search through the record to find specific things.
Re:Sorry, we can't join your Slack
by giancarlostoro on Saturday September 07, 2019 @12:15PM
(#20904696)
Jira has the ticket description section which gets updated to the latest goals / spec as things change. The history is for context of "who said do this" / "why did we do x"
The last three companies I've worked at had the same rule, except with no exceptions. All discussions get recorded into the system, precisely for the reason that you state -- so there's a historical record of what was discussed, what was decided, and why.
Any "external" communications, such as with email or IM, are expected to be copy/pasted into the system so its permanently recorded in a useful way.