Who is claiming that if a bug fix fixed and not documented meticulously in JIRA it is as useless as if it was never fixed at all?
That's not my intent as the parent here, or the point I'm seeing or picking up from this thread. There's value in documenting in a system (Jira is one choice), but I know that I'm certainly able to see value in building a system and a process and then trusting that developers use them when appropriate and know when they are not adding value.
Re:Why Jira Sucks
by stefanmichael on Thursday December 31, 2020 @02:35PM
(#25596241)
The original poster in the thread we're in:
"Fixing a bug or delivering a feature where you haven't documented the process ... is as good a running a web site nobody visits."
The necessity for documentation exists along a spectrum, and the means of documenting things exists along a spectrum. We have lots of tools for documentation. Design docs, commit messages, the commits themselves, JIRA, email, chat. Which one is appropriate depends on the given situation.