And, again, issue threads are only helpful if the people corresponding in them are good communicators who put in the work to leave a legible record of what happened.
Many Github issue threads that I read are incomprehensible. The thread is not where the story is (it's in the memories of the people involved). Explaining is work. This is why they make kids write reports as assignments in school.
Typically this is what product managers and stuff are for. They stick around pretty much just to organize the Jira and make sure everything is fleshed-out. I think if your git frontend links commits to Jira (ours does) AND you have pretty strict requirements for your Jira items it can work out.
It seems like the “why” is eternally lost on us in this scenario.
If I could wave a magic wand and make all the colleagues verbalise what they’re doing, I would.
In the meantime, I’ll take the downvotes for pointing out that it’s fundamentally caused by a cultural gap, not just “those who don’t get it yet, and those who do.”
