I think our disagreement comes from different understandings of what you meant. When I think of "no code without a Jira ticket", I usually don't mean "create a

I think our disagreement comes from different understandings of what you meant. When I think of "no code without a Jira ticket", I usually don't mean "create a Jira ticket for the code", I mean "find the Jira ticket that links closely to the code you're writing". I do agree that creating Jira tickets all over the place creates unnecessary work for everyone - even those trying to read the reports. It is helpful, however, to know the general area and background for the code you've written e.g. what the feature is and any comments on it. Stuff like "developer X was working on feature Y when he wrote that code".