Has anyone used CA's Rally for issue tracking? Is it as bad for devs as I've been warned?

We are being forced to use it instead of Jira because of the pretty reports it generates for management and I am kind of scared...

We use Jira and I think it's tracking capabilities are sufficient

@developerTom: I agree. And the integration with Bamboo for build management is priceless.

With Rally we do that and it is my understanding there are no fix/affects version fields, custom workflows, and more.

But we are being forced to use it for reports it generates. I'm pushing back. Hard.

I just want to make sure I'm not overreacting.

If I was asked to use a new library I've never used I'd be totally fine. But changing our entire workflow for issue tracking/sprint planning/deployments with no transition? Ugh.

Yeah I totally understand, in the grand scheme of things are reports enough of an issue to restructure an entire workflow system.. I think not.

*lose that, not do that

@developerTom glad someone understands.

I'd love to get someone's experience of Rally on here. Right now I only hear the whining of my neighbor at work, but he whines over everything... So I am not sure if it is justified.