Was happily using Bugzilla but the company decided to switch to Jira and it's unpleasant to put it politely.
One of my main gripes is the ability to atomically update an issue vs incremental updates. For example, Bugzilla allows you to edit multiple fields then hit commit to save, Jira on the other hand applies changes automatically when you edit certain fields (e.g. assignee). This causes people problems (person gets assignment email before the comment about why it was assigned to them has arrived or vice versa), and automation problems (if you have anything driven by receipt of the emails, you now need to collate many before action can be taken). It may well be possible to configure Jira in a way that's more useful to us, but sadly we've got one mega instance that's supposed to be all things to all people and as such, doesn't do many things well!
Used Redmine before Bugzilla and thought that was pretty good.
Yes, good thing to point that out. It can be a great help in some cases, but unfortunately that modal dialog blocks access to the comments on the bug, so composing your reply in it can be frustrating.
Yes I can compose my reply in another editor and paste it once it's final. However, IMO an issue tracker is something you use so often that working around these small issues comes at a high cost to me when it should not.
Yeah, I agree that the UI and modal abuse could use some work. I still prefer it over most other issue trackers, though, because it can be queried as a database.
It supports any type of filtering you could need. It hides the complexity of what I assume behind the scenes are table joins. It's not for quantitative reporting but rather for retrieving manageable lists of relevant issues out of a data base of hundreds to hundreds of thousands. What sort of query would you want to run against an issue tracker that you don't see supported there?
One of my main gripes is the ability to atomically update an issue vs incremental updates. For example, Bugzilla allows you to edit multiple fields then hit commit to save, Jira on the other hand applies changes automatically when you edit certain fields (e.g. assignee). This causes people problems (person gets assignment email before the comment about why it was assigned to them has arrived or vice versa), and automation problems (if you have anything driven by receipt of the emails, you now need to collate many before action can be taken). It may well be possible to configure Jira in a way that's more useful to us, but sadly we've got one mega instance that's supposed to be all things to all people and as such, doesn't do many things well!
Used Redmine before Bugzilla and thought that was pretty good.