[vinaypai]

In my experience, Jira isn't great out of the box but it's pretty good if you take a few hours to understand how to configure workflows, field configurations, forms, and boards.

For example, at my last company I had the development project configured with about a dozen different ticket states, but you created a ticket with a simple form with the title as the only mandatory field but there were optional fields for details and screenshots.

Developers could move a ticket into "in progress" or "can't reproduce". The latter transition showed a form with a mandatory explanation field, and it would automatically get assigned back to the person who created the ticket.

On completing the ticket, the developer has to put in a pull request and can only moves it to the Code Review state and had to pick a different developer to assign it to.

It sounds a bit tedious when you describe it but in practice everyone worked off a board with three or four columns appropriate to their role. They move tickets to the right to advance them or to the left to reject them. There were also automated transitions triggered by things like CI tests, deployment etc.