I dislike Jira, but it's quite untrue that it's absurd that there needs to be context and a record of discussion for tasks. People leave, focus changes, memories fade.

It's not a unique occurrence that I wonder "why the hell is it done like this?!" only to find it was a decision I was part of with developers who had left in a least-worst-change trade-off. Jira or products like it help us avoid repeating the same mistakes.

Put another way, part of the art is not just the code, but the code that's not there. Jira/tickets are one way of managing that data.

And at other times, it's just a tool for bureaucracy, I get that.

heh you would be surprised. I literally closed a ticket from 2014 this week which had a lot of relevant information and prior discussion. Without the record of it somewhere I would of had taken much more time.

I also always search jira for a particular issue that I am having to see if someone else has already solved it or a reason for it not to be solved. Sometimes it works quite well saving me a lot of time.

... have you ever worked on a project involving multiple teams?

I say this as someone who loathes JIRA but still exists in the real world where you need to collaborate to design something.

You might actually be the assembly line robot if your work is so simple that you can do it without any sort of planning, design or collaboration.