2 ms·

I just switched our team to JIRA for this exact reason. We were already on Bitbucket for repos and using Sourcetree for git access, so might as well get issue t

by quasse 12y ago

I just switched our team to JIRA for this exact reason. We were already on Bitbucket for repos and using Sourcetree for git access, so might as well get issue tracking from the same place. Honestly my feelings on it are mixed so far. Doing a "good" job of administering projects and issues seems to have a pretty steep learning curve if you want to use more than about 10% of JIRA's functionality.

matwood 12y ago
Basic ticket management is easy to get going. Users of the system can also mostly get away dragging tickets between status and logging some work as long as the Greenhopper plugin is turned on. JIRAs biggest win is integration with so many other tools. Bitbucket is an obvious one, but then 3rd party tools like bugsnag will auto-create tickets for any snags your app issues.
danieldk 12y ago
Doing a "good" job of administering projects and issues seems to have a pretty steep learning curve if you want to use more than about 10% of JIRA's functionality. That's why I like Youtrack more. It's far less complex and driven by search plus keyboard shortcuts.