I think if you need a tool to "keep them honest" you may have a major culture problem in your company. We started our company to make a tool where people collaborate to get stuff done together, not to be a place where managers keep tabs on their people.
That being said, despite that I personally don't love Jira I do think there are some cases where you need particularly complex workflows (e.g. compliance use cases) where Jira's complexity is fully justified.
And we know our tool is not for everyone. If your team is happy using Jira, power to you. But I think it really is important that the team is happy with it, not just the bosses.
> I think if you need a tool to "keep them honest" you may have a major culture problem in your company.
What kind of organization doesn't have real OKR's or performance metrics? Do you draw a pretty picture with sunshine and rainbows and report that to investors?
You said developers don't like Jira because it's there to "keep them honest". I don't think micro managing your people via an issue tracker leads to better performance on OKRs.
I report actually meaningful numbers to my investors in terms of value delivered to users, not number of tickets churned through.
That being said, despite that I personally don't love Jira I do think there are some cases where you need particularly complex workflows (e.g. compliance use cases) where Jira's complexity is fully justified.
And we know our tool is not for everyone. If your team is happy using Jira, power to you. But I think it really is important that the team is happy with it, not just the bosses.