[NickNameNick]

I must be in the 'baffled' group, my employer moved to JIRA, and it's been a nightmare ever since.

In particular, because time reporting and billing decisions are made at the project level, and there is only a single list of projects, with no inter-project relationships, as opposed to other systems (redmine, etc) which feature hierarchical trees of projects, basically every interaction with the system is harder than it needs to be.

Also, 'smart commits' are hideously clunky, when it works at all, which exacerbates the issues above.

I certainly wouldn't recommend it to anybody, and in fact have strongly advocated against it.

[manyxcxi]

JIRA and Confluence are fantastic at doing their core competency but there are a lot of fringe features that just seem bolted on because some big time customer or PHB decided to bolt on things. I found the time keeping to be one of these things, as well as smart commits- but I think the smart commits problem is just a matter of iterating the feature and making it 'smarter'. I think it will eventually be enormously useful.

My experience has been that if you have competent implementors and administrators of JIRA and Confluence together, and use them primarily to run projects they are very nice and they interplay very well from requirements and documentation in Confluence to tasks and WIP tracking I'm JIRA. But if you implement a crazy JIRA workflow of your own that isn't completely smooth or organize your projects and documentation in a way that JIRA/Confluence don't really get- you're going to have a jumble of buttons and hoops to jump through and your users will hate it.