this post was submitted on 24 Nov 2025
234 points (98.8% liked)
Linux
11022 readers
420 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is not an example. What type of communication? Are you classing emails? Are you classing internal documents? Are you classing marketing material? Are you classing internal comms?
This description screams "use a proper ticketing system" to me but, again, I feel like I don't have enough information about the process you're talking about.
A badly designed process or the wrong app.
Again, this all sounds like you guys are using the wrong tools for the job, but would need to hear more details.
Im done. You have utterly no idea what you a talking about. Fundamental information management concepts are foreign to you.
And you seem to think that "ticketing system" can only be used for IT incident management. It's like you're not aware of integrations with (or flat out specialised tools for) knowledge management systems, HR systems, CRM systems, asset management systems, and a billion others.
You still didn't give me any example of a process you had in mind so, yeah, I agree, the discussion is pointless.
Great story never said that.
Go do a course in basic information management.
No need, we have a tool for that. One that's decidedly not email....
No doubt its a ticket system
Yes. It's a system where we can create an entry for every case, monitor it, log all activity, manage who's responsible, who needs to approve, and who owns which parts of the process, automate everything that needs automating, and - in case of an audit - present the entire lifespan of the case, from start to finish to the auditor.