I've used both, and plenty of other tools. I really think these types of tools need to be aligned with the type of team you have and the workflow you plan to use. There are a dozen tools that will fit the bill on a feature breakdown. With real-world use, with your team, with your project, with your environment, you'll discover a clear winner.
Some notes on products I've used, for reference:
FogBugz: A few years ago it was reasonably lightweight and decent. It's gotten more complicated over the years and I couldn't stand it the last time I checked it out.
JIRA: The "enterprise" solution. Infinitely flexible, with all the positive and negative aspects that go along with that. Best API of all of them, though, IMHO.
Pivotal Tracker: I've used Pivotal several times over the years, and to be honest the UI is very cumbersome to use IMHO, and the density of features make it fairly heavyweight to use.
AgileZen: My personal all-time favorite for managing development projects. Fits a kanban-inspired mould, which I tend to like quite a bit. JIRA offers a kanban-board view as well, BTW.
If I were you, I'd sign up for free accounts for all of these and use them for a week or so. It's the best way to find out if you like how the tool operates and if your team will actually use it, which is more important than any specific feature.
I'd also take a second look at your requirements. I wouldn't discount a SaaS tool for no reason. SCM integration (svn, git) can sound nice, but to be honest I've found that it adds too much friction to the commit workflow (to add a story ID or whatever) and is usually of little value).
Some notes on products I've used, for reference:
FogBugz: A few years ago it was reasonably lightweight and decent. It's gotten more complicated over the years and I couldn't stand it the last time I checked it out.
JIRA: The "enterprise" solution. Infinitely flexible, with all the positive and negative aspects that go along with that. Best API of all of them, though, IMHO.
Pivotal Tracker: I've used Pivotal several times over the years, and to be honest the UI is very cumbersome to use IMHO, and the density of features make it fairly heavyweight to use.
AgileZen: My personal all-time favorite for managing development projects. Fits a kanban-inspired mould, which I tend to like quite a bit. JIRA offers a kanban-board view as well, BTW.
If I were you, I'd sign up for free accounts for all of these and use them for a week or so. It's the best way to find out if you like how the tool operates and if your team will actually use it, which is more important than any specific feature.
I'd also take a second look at your requirements. I wouldn't discount a SaaS tool for no reason. SCM integration (svn, git) can sound nice, but to be honest I've found that it adds too much friction to the commit workflow (to add a story ID or whatever) and is usually of little value).