[grey-area]

If you spend more than a few minutes a day struggling with Jira, you should bitch to whoever is in charge of Jira. But if you really believe that 15 minutes a week of your time

This doesn't reflect my experience at all as a developer in small teams.

I spend quite a lot of time in the issue tracker - it is one of the main ways (along with email and conversations) that I interact with other team members and track work in the team. I can't imagine any situation where developers would spend just 15 minutes a week in an issue tracker and be able to do their job effectively, even junior devs should be spending more time than that responding to feedback and explaining what they have done, scope changes, what to test etc etc.

Creating software is not all writing code - much of it is thinking and interacting with other people, before you even start writing code, and then iterating fast on what you have written, gathering feedback along the way. An issue tracker is one of the tools used to do that.

So the tools are important, and Jira gets almost everything wrong in my view.

[MegaButts]

I'm not saying you shouldn't spend more than 15 minutes a week documenting, discussing, and diagnosing bugs and developing features. I'm saying you shouldn't spend more than a few minutes a day having to wrangle Jira. If you want to find a bug that's relevant to you, it should literally take 1 second for you to load the page that tells you your sprint and backlog and start looking at it. All of this should be managed by a program manager. You shouldn't have to repeat anything from GitHub. You shouldn't have to go digging for bugs to work on. You shouldn't need to go looking for documentation. All of these things are supposed to be done by someone else.

> Jira gets almost everything wrong in my view.

What specifically would you like to be different?