Developers will love it, others have to go along for the ride
Updated April 08, 2015

Developers will love it, others have to go along for the ride

Anonymous | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User

Software Version


Overall Satisfaction with Atlassian JIRA

We're using JIRA across the organization to build digital products in Agile with onshore and offshore development teams.
  • Planning board allows good visibility into sprints as well as backlog, making it easy to organize and prioritize
  • Integration with Confluence allows easy cross-referencing between Product Requirements and User Stories
  • Integration with HipChat allows for asynchronous communications across time zones.
  • Information Architecture between JIRA and Confluence is abysmal, can be difficult to navigate between the two
  • OnDemand instance has limited add-ons.
  • HipChat would greatly benefit from a shortcut that links issue numbers directly to tickets
  • There is a steep learning curve with JIRA, both for admin set up and users
  • JIRA OnDemand doesn't scale proportionally, adding one new user over a certain number doubles the monthly cost.
  • JIRA has allowed us to move quickly to achieve our goals
Personally I would prefer a simpler tool, the decision to use JIRA had been made prior to my joining the team.
I think JIRA works best for developers, whereas designers and other team members prefer tools with a more intuive user experience, like Basecamp.

Using Atlassian JIRA

We move very quickly with a large team that is already familiar with JIRA and the process we established with it. We may not be able to afford the time required to transition to and and become equally proficient using a new tool.

Jira Implementation