This question can only really be answered by your project lead, or whoever is in charge of the "ticketting process".
But let me ask the other way: why would you not record a bug you patched?
The only fathomable reason I see is that the effort for filing the bug report, committing against it, and closing it, is orders of magnitude larger than the time to fix the bug.
In this case, the problem is not that the bug is so easy to fix, but that the paperwork takes too long. It really should not. For me, the overhead to create a Jira ticket is pressing
c, then entering a short 1-line summary, and pressing
Enter. The description is not even overhead, as I can cut&paste that into the commit message, together with the issue number. At the end,
. c <Enter> and the issue is closed. That boils down to 5 key presses overhead.
I don't know about you, but that's little enough to make it a policy in even small projects to record every bugfix in this way.
The benefit is obvious - there are quite a few people who can easily work with a ticket system like Jira, but not with the source code; there are also reports generated from the ticket system, but not from source. You definitely want your bug fixes in there, to learn about possible developments, like a steadily increasing influx of small 1-line bugfixes, which could provide you with some insight into process problems or whatever. For example, why do you have to do such small bug fixes often (assuming it happens often)? Can it be that your tests are not good enough? Was the bugfix a domain change, or a code error? Etc.