If you need the distinction, label it "discussion" instead of "chat", and assume that important discussions need to be kept around for reference.
We have tons of one liner tickets with only a title and a link to a Slack thread, and it saves crazy amount of time and effort.
You could accomplish the exact same thing you’ve done by pasting the Slack discussion into the ticket or a text file with a link. Except you’d now control your future. So you’ve saved less than five seconds by copy pasting a Slack link instead of highlighting a bunch of Slack messages to copy paste.
I see this as the same philosophy as leasing computers or company cars, relying on third party delivery companies to ship your goods etc. It's a business choice, and solving some of your problems with money is usually a valid strategy. When it stops making sense you reevaluate your options, check competitors etc.
PS: on pasting Slack text into tickets...it's really not optimal. If you really want the info in the ticket, spend the time to write a clear summary and still link to the original discussion. Formatting gets lost, or you're sticking screenshots of whole threads which is still horrible.
To note, our ticketing system is basically a fancy reminder/todo list and we're not SCRUM, if that gives more perspective into why time spent writing detailed tickets hasn't a stellar ROI.
Surely, you meant to say "Slack used to be permanent...".
It's a valuable lesson that, it seems, each generation of engineers gets to learn anew. If it's not under your control (direct or contractual), you will lose it at some point.
For instance I can't think of any document or design discussion I wrote in the past 10 years that would still matter today. Either the system is still somewhat live and running, and it's probably too far away from the original design for these docs to matter, or it's dead and buried, the company potentially not existing anymore.
In a way, actual permanentness is overrated for many many applications.
Now, people would be more sensible to disruptions of the current business, but arguably services like Slack or JIRA have a better track record than home made internally managed systems.
Did you know that SLACK was originally an acronym?
On Slack, there's no such thing as a discussion-level subject, and people frequently end up replying outside the thread, or at a minimum there's other context outside the thread that people don't bother linking to because they think of chat as ephemeral, not that they are constantly building up an internal wiki.
There are often more durable options like a forum within the community, but that doesn't stop the Slack companion community from having high value discussions.
You often don't know you're having a conversation worth having until it's done. Kind of like when you see really good discussion in Stack Overflow comments that you wish were upgraded into a community wiki question, but that's not how it emerged.
Chat needs to be ephemeral.