TrustRadius
JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.https://media.trustradius.com/product-logos/Do/VE/SNKZVM5Z3C0V.PNGGet agile with JIRA SoftwareMultiple teams within our organization use JIRA Software, including Product Content Strategy, Product Design, Product Education, Product Research, Front End, and Dashboard. Each team uses JIRA a bit differently, and each team's "project" is therefore set up a bit differently, but all of us follow a kanban agile structure. JIRA helps us stay on top of our tasks, view progress, and ensure all necessary work gets done on time.,JIRA offers a lot of integrations that really improve our work. For example, the Salesforce integration makes it really easy to link Salesforce product roadmap cards (relevant to the entire product team) to an individual JIRA issue (one specific task-relevant to that team). JIRA offers very good search and filter functionality. The quick filters make it very easy to immediately see only my own issues. You can create custom views, which are especially helpful for my team during our daily standup, allowing us to only see relevant issues. JIRA issues come with lots of customizable fields. Due dates, assignees, labels, priority level, epic link, etc. -- makes it very easy to organize and find specific issues.,Our team happens to have many steps within the workflow, and therefore we have more columns than other teams. JIRA Software always displays all columns in one static view. Because we have so many columns, each column becomes very skinny and the issues can be difficult to parse. We can't reduce our number of columns, so I wish we had the option to side-scroll instead of fitting all columns into the current browser size. We would love the ability to create CLEAR multiple statuses within a column. You can create multiple statuses for a column, but they all appear together and are difficult to distinguish. It isn't possible to move an issue from one status to a different status within the same column. You have to drag the issue into a different column, then drag it back into your chosen status, or change the status using the issue dropdown option. A minor nitpick, but I wish I could create an issue and immediately put it into our "To Do" column. Instead, it automatically goes into our backlog. Then I have to go to a different page to move the issue from backlog to To Do.,9,JIRA Software streamlines communication between different teams -- I can look at other teams' JIRA projects to see the status of individual issues without having to directly ask any colleagues. JIRA exponentially improves our team's productivity. We have a daily standup where we go over our JIRA project, and this allows us to focus on slow-moving tickets and identify blockers. It really helps to see the issue "physically" moving down the line, closer and closer to finish. JIRA improves our team's visibility. Often it feels like our work goes under the radar, but with JIRA, other teams can track our progress and view our contributions to new features.,7,7,Trello and AsanaJira for Enterprise BusinessJIRA is being currently utilized as a second tier ticketing and workflow management system. Our users create a ticket in our regular ticketing system for an enhancement and such. Once it has been approved a ticket and sub tasks with all the detail are input into JIRA and tracked. We then use JIRA in our weekly meetings to give updates and such.,JIRA makes collaboration very easy JIRA allows us to keep a line of sight on all of the tasks that are on going JIRA also allows for easy export of data for reporting and such,The UI In JIRA is not very intuitive, they have comingled products and navigation is difficult at times JIRA can be annoying with the number of email notifications it shoots out JIRA's security model is overly complex and can lead to issues,5,JIRA has allowed us to create reports on tasks and deliverables so this is helpful We spend too much time attempting to create the reports so this is a negative JIRA has help us meet some of our auditing requirements,4,5,,SAP Service Cloud, ServiceNowJira makes agile software development management easyWe use Jira as the product management tool for our agile web team of about 12 people that are doing a major redesign/rebuilding of our city's main website. It's used to plan and track the individual tasks, stories, and bugs assigned to each team member. It also provides helpful reports showing our sprint velocity and other useful metrics.,Jira is powerful and flexible. It can be configured and used in a number of ways and for a number of different use cases. But despite that, we've found it easy to use and we were able to use it without much training. For agile-based software development, it makes it easy to manage your backlog, plan sprints, track and manage individual issues, and get reports showing overall team/sprint metrics. All of these features are seamlessly integrated with each other. It integrates well with other developer tools like Github and Slack. For example, this makes it easy to view branches and pull requests related to a specific story or automatically notify your team of important status changes to an issue.,Sometimes there are different modes for editing the same piece of data (like an issue's description) depending on how you're viewing that issue. One mode may use a WYSIWYG editor while the other mode uses plain text with Markdown. This is slightly confusing as the user experience isn't consistent. As with most WYSIWYG editors, it can sometimes be difficult to control the formatting the way you want. I've also had issues with it inserting line breaks after hyperlinks sometimes for no apparent reason.,8,As a team switching to an agile-based methodology, it's helped us to follow our desired agile practices and has made it easy manage our processes. It's helped our project to stay on track and has been recognized as a successful pilot with our organization. Other teams within the organization have seen or heard of our success and are now looking to implement some of our same tools and practices, including Jira.,8,9,Redmine and Basecamp,Eclipse, Google Drive, DropboxManage your projects with a simple and easy to use interfaceIt is being used throughout our organization. We use it to plan, monitor and develop your projects quickly and easily. With Jira, plan your daily work by creating user stories, incidents or assigning tasks and subtasks to your team members. Integration with the main development environments such as Eclipse, Visual Studio, Netbeans, make it an effective and productive alternative.,It is very simple, basic and simple to use. It allows precise customizable estimates according to the needs of the project. You can have administrative control of the company's activities (projects, processes, procedures). It is compatible in virtually all databases. It offers Web access with support for the main browsers in the market, email notifications, as well as many applications that provide additional resources to Jira.,Although Jira is an excellent tool for project management, the cost can be somewhat expensive. Its initial configuration proved to be complicated. It can be difficult for beginners, because it is difficult to understand its characteristics.,9,Workflows can be customized and adapted to our needs. It substantially improves teamwork and communication between users. Increase productivity, as it helps to plan, specify and follow the work of my team members.,8,9,Basecamp and Zoho Projects,CylancePROTECT, Zendesk, Lexmark Managed Print ServicesJIRA worksJIRA Software is used by the website development group. It tracks our new projects, our system bugs, and system problems. We use it to communicate with our workers who are off-site. We also use JIRA with Github to number our Git branches. Using JIRA's ticket codes keeps everything in sync and reduces problems.,Project tracking Individual task tracking Integration with Github,Communication with team members is adequate but not as good as other software Not as many software integrations as I would like Can't delete tasks unless you are super user,8,Project teams are able to work more effectively. Keeps team on task,8,8,Yes,Price Product Features Product Usability Third-party Reviews,I would more fully evaluate the softwares integration with other third party applications.JIRA for an easy kickstartI have experienced JIRA in two major areas: 1 ) a tool supporting internal users or client requests (internal or external service desk/help desk). 2) a teamworking tool for the sharing of software specifications during software development.,Excellent tool for supporting internal or external users. If you want to start, you can go to the cloud/online subscription which is very cheap and you can start immediately with preconfigured processes Great tool for sharing business and IT requirements in SW development. Requires connection of JIRA and Confluence which works fine after initial configuration. Available basic reporting of performance of teams or individuals. An immediate good overview of severity (priority) of tickets, resolutions KPIs, etc.,The processes can not be thoroughly analyzed, visualized and managed. Although a basic reporting is available and reports can be customized, the process discovery in a complex environment is not supported. This can, however, be provided by an external process mining application. JIRA can export the data or provides access to its database via API.,10,This tool can save a lot of money by visualizing project progress, regardless if you develop in a waterfall or agile mode. Imagine saving just 1 day on a project with 50 programmers just by being able to recognize an issue in development. The monthly subscription fee per user was back in 2018 a peanut.,9,10The winning combination for your software development team: JIRA + AgileWe use JIRA as a project management and a bug tracking tool for most of the company projects. Whether it is software development, ASIC design or IP development, JIRA fits all flavors. For software development, we use it mainly for its agile scrum and Kanban development support. We realized that switching to Agile with JIRA was a winning combination to increase productivity, together with having more homogeneous teams and same mindset across team members.,Easy to use bug tracking features. It has a great support for Agile SCRUM and Kanban software development methodologies. Promotes collaboration within the team and across teams. It is extremely configurable and allows a system admin to address complex project management requirements.,There is a steep learning curve for JIRA administrators before the full potential of the tool can be harnessed. The licensing system is per number of users. If you buy a small license and the tool is widely adopted, you may have an issue in getting your budget approved in a low cost environment, because the price for higher tiers goes up quickly. Support can use some improvement. It happened few times that for critical issues we had to spend a lot of time exchanging emails and explaining to different people where the problem was.,10,It really improved our productivity and therefore decreased the time to market of our deliveries by 40%. It improved the collaborative work inside the team. Helped building the scrum mindset in the team. It helped replacing the various bug tracking tools used across the company to just one.,9,7,BugzillaJIRA -- The all in one cost-effective and integrated project management solution for our OrganizationJIRA is used in my organization for tracking issues from production support by our support team. For customer delivery and platform development teams, JIRA is used for bug tracking and to create stories and features for building solutions and the product. It is serving as a product management software, and for solution delivery teams it is our primary project management tool. We have scaled and customized JIRA to several teams in our organization, and it is a very cost-effective solution for tracking all business issues from product development to production support.,Bug life cycle management. Grouping of deliverables as: epic, story, change request, bugs, tickets, enquiries, etc. Logging estimates and tracking actual efforts, giving effective variance computation. Computing metrics for our projects using the custom fields in JIRA.,The SLA management is ineffective. The assignee has to be an individual, which is a restriction. JIRA needs to enable issue assignment to a group/department as well, to bring it to an issue dashboard. Query management can be made easy with some add-ons like 'Script runner' which is currently outside JIRA.,10,Prompt delivery. Following SAFE methodology via the Portfolio add-on in JIRA. Provided a cost-effective solution to track from product development to production support.,BMC Remedy Asset Management and ServiceNow,Bugzilla,9,10A Project Management tool for your organization and clientsWe're using Jira as a tool to be in control of our projects. We use it for tasks and much more. We use it across all of our organization and highly appreciate the options of integrating Jira with Bitbucket. It's important to stay agile and Jira does the job. We can use the software between departments - design, development, etc. Our project managers have the option to get a better idea of what we're doing and how much time we're using during the tasks.,Tasks Project management Agile boards Ticketing for problems etc. Complex user management.,User management can be to complex for non-trained users. Very expensive. Could services sometimes crash?,8,Satisfied clients. Better collaboration between offices. Steep learning curve - so a time used on the training of new users.,Asana, Gitlab and Trello,Asana, Bitbucket, GoToMeeting, Adobe Acrobat DC, Adobe Flash, Adobe Illustrator CC, Adobe Experience Manager, Adobe Photoshop, RescueAssist, WordPress, Microsoft 365 Business, Microsoft Teams, Egnyte, Samanage, Sophos Intercept X, Sophos Phish Threat, Sophos Web Content Filtering, Sophos Secure Email Gateways, Sophos Mobile, Cisco Meraki Systems Manager, Basecamp, Zeplin, Sketch, Cisco Webex Teams (formerly Cisco Spark), Cisco Webex Room Series (formerly Cisco Spark Room Series), Microsoft Teams, Skype, Skype for Business (formerly Lync), Microsoft Project, Microsoft Visio, Microsoft Visual Studio Code, Azure Active Directory, SurveyMonkey, Google Hangouts,9,9JIRA is a great project management toolJIRA is being used in our organization to manage software development. It is used to easily manage the workload. It makes our developer's job easier as they can get all the information from the JIRA stories. JIRA is also used to check the status of the project and manage assignees.,Easily manage workload. Get all useful information and links to useful documents. Check the status of a project. Integration with Git.,There is no code refactoring plugin. We can prioritize the projects. The user interface makes it a bit complex to search for all items.,9,JIRA makes project management seamless. Developers and managers are updated with project progress. All documents are accessible easily which makes for a hassle-free process.,9,9,VersionOneJIRA - Managing a Project Activity at your Fingertips!JIRA is used by our Company to setup Epics and the associated Tasks that belong with the Epic. We then plan our Sprint (2 weeks) with Development tasks and track the progress of those tasks. If something happens that hinders the development of such task, we can easily put a block on that Task until the block can be removed (i.e. waiting on data cut from Agency). We can easily drop something into the backlog when needed.,Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed. Notifications can be automatically sent out (if setup) to the Developer when new work is assigned. Epics/Tasks/backlog items can be managed through an easy to use drag and drop process. Agile. Easy to work with (very intuitive),I don't have anything negative to say about the software. As with any software, the GUI can always use improvement, but that comes with time. It can lock up very briefly at times due to too many users.,10,We can manage 100's of projects at a time. I work on a DB Conversion Team and it can get a little hairy trying to keep everything straight. JIRA does that for us. JIRA is easy to use and there is a very little learning curve for new team members. JIRA allows for a 40,000-foot view or a 5,000-foot view. You can drill down as deep as you need to go, or take a step back and look down from the heavens.,10,10,Logitech Rally,Changepoint, Microsoft Office 365, Microsoft ProjectJIRA: A great bridge between PM and R&DOur organization uses JIRA as a project management tool between our project management office, our product management team, and our research and development team to plan, coordinate, and deliver on product releases encompassing multiple initiatives, epics, features, users, stories, and tasks. Each team is responsible for various components of a release from inception to end-of-life.,Organization of features Story development for R&D Release candidate control,Ease of searching Editing Process flow of feature development Acceptance Criteria development,8,Better organization for feature releases. Linking to issues and enhancements has increased ROI from releases. Customer satisfaction improved due to the adoption of continuous release model.,7,8,Microsoft Visual Studio Code,Microsoft Teams, Skype for Business (formerly Lync)JIRA is the most easy to use project management software out thereWe use JIRA to manage multiple high-level projects within our company. It is a corporate-wide engagement with JIRA with several businesses that use it independently with a corporate administrator to manage the tool. We use it for very large projects, like Salesforce rollouts, as well as smaller projects like minor enhancements or bug fixes across all key software environments.,It is a great tool to link documents and documentation to specific user stories to keep things organized. It has a great user management feature to help us plug resources into the right projects and remove users as they move on to other work. It has sold plug-and-play options that you can elect to use or deselect in order not to cloud the interface.,The look and feel is a bit sterile, which is both good and bad. Some nice skins to make it easily customizable to our existing corporate color schemes would be nice. Cost is always a place for improvement. JIRA is not overly expensive, but in a market where there are a ton of options, price is a negotiation point. Better integrations with vendor/partners using the same tool would help onboard offshore resources we occasionally use.,10,Better prioritization of user stories and resources. Better tracking of resources. Better documentation container to store relevant information.,9,10,Basecamp, Workzone, VersionOne, TargetProcess, Pivotal Tracker, Assembla Workspaces and SprintGround,Basecamp, Workzone, SprintGround, ActiveCollab, Assembla Workspaces, Attunity Managed File Transfer, Sopheon Accolade, Cloudera Data Science Workbench, Snowflake, Qlik Sense, Qlik Sense Cloud, QlikView, Microsoft Power BI, Informatica Cloud, Informatica Enterprise Data Integration, Salesforce CPQ (formerly SteelBrick), Salesforce Service Cloud, Salesforce Marketing Cloud Email StudioJIRA - adapts to your software development process!JIRA has been a great replacement for Microsoft Team Foundation Server. Not only is it easier to use, but it's highly customizable by our organization without the need of external consultants. Bugs or feature requests are created throughout the whole company and then triaged into actionable tasks. The filter feature on the system dashboard helps a lot in this context.,Custom search queries can be saved and shared as filters. Batch operations on tickets work well and you can choose if you want to notify others. Ticket fields are highly customizable for easier creation.,Some operations take their time. Default ticket settings are too complicated and complex for simple use cases. Basically, there is no "one go to process". You can pick Kanban, Scrum, ... whatever you like. The user interface, therefore, looks quite mixed up on some occasions.,10,Development pace has been greatly improved. Visibility of progress for better understanding of the development process. End users are more likely to open up feature requests or bug reports.,Azure DevOps Server (formerly Team Foundation Server), Usersnap for QA and Pivotal Tracker,Usersnap for QA, Google Analytics, Slack,10,10All around change management tool with lots of featuresProject and change management with issue tracking is crucial for safety-critical software development in aerospace industries. JIRA provides many of the project management and agile process needs with a lot of features such as sprint boards, dashboards, filters, and reports. You can customize our own workflows and boards according to your own needs. Kanban boards and sprint boards are especially useful for big team projects.,Agile development with sprint boards. Versatile filtering and customization of projects and reports. Easy and simple user interface.,Filters could be more descriptive. Could be integrated with requirement management software for direct navigation. More 3rd party add-ons could be better.,9,Change management is done without problems at all levels of a project. It is widely known and accepted within aviation authorities. Its easy of use made it possible for even a new graduate to use it effectively.,IBM Rational DOORS, MATLAB, ANSYS SCADE Suite,8,9Jira PM reviewJira project management system is used to manage project tickets. It's used across departments, and helps prioritize work.,Flexible in building interfaces for different teams Powerful archive provides historical data for past projects in case they need to be retrieved Links to different software to easily load information and build tickets faster,Interface is outdated and not easy to use, which makes it slower to work with the tool Ticket linking is not very flexible, so it's not easy to reference work to other department work in progress or past Overall system is very technical, making it challenging for more non-technical teams to join and use the tools,6,Positive: organize work, prioritize tickets Negative: takes a long time to work with the team, not easy to learn functionality Positive: Very good archive tool to reference past projects,Asana,2,5JIRA and Agile for you businessWe use JIRA to manage/track projects across the whole organization. It is a well documented tool and helps our team members to keep up with the workload as well as generate KPIs to higher management and provide a better visibility on what needs to be done throughout the projects. I would say it is an essential tool.,The high level of customization on this Agile system is key to meet different niches and industries. You can configure to use on any project you wish to take on without any effort. A system you can learn from. Jira collects and unites all historic data in a single, searchable hub, and provides access to it at any point of time. This way, team members will be able to perform all sorts of rend analysis and statistical investigations, and prepare constructive reports on their progress. A rich toolkit for developers. While it is true that Jira is mostly appreciated for issue and bug tracking, those are far from being the only features you should know about. This system will become your developers’ favorite assets before you know it.,The UI is a bit confusing sometimes to the inexperienced user. The price can be a little too much for small businesses. Too many features, that sometimes can bring some complexity to the platform (this is sometimes rated as a good area too, it will depend on how experienced [you are] and the points you want to cover with this tool).,9,We have seen a faster ROI on our products as the production processes have been optimized.,Trello and Onyx,Atlassian Confluence,7,9JIRA is the BEST software collaboration toolWe use JIRA as our company's main project management tool, this integrates development and QA to plan, track and report progress of our software releases.,An effective tool for planning/tracking work from project backlogs and Sprint An effective tool for tracking defects Fully customizable Kanban and Scrum boards Easy to maintain the integration of defects and test using a test management tool like QAComplete.,JIRA is fully customizable, although we were able to make our QA process fit into JIRA's workflow, it is not designed to work like this. Not easy to make it work as a test management tool.,9,The user must be familiar with creating the workflow in order to make the automation process run smoothly.,,Atlassian Confluence,9,9Jira = collaboration, integration, usability.Jira, at a high level, is being used by our technical teams (engineering, support, implementation) to track development efforts, product feedback from our clients, as well as Dev, QA, and production efforts to get our clients up and running. In addition, of course, to tracking bugs in our product. Jira allows us to collaborate across all of our teams as well as keeping us all apprised of the progress of each individual project or longer-term initiative.,Tracking projects based on assignee (ie: the person who needs to take action on a ticket). Easily seeing how many product tickets are open at any given time. Planning and road mapping of your product, Jira makes it very easy to track priority with development effort, you can display it easily on a map.,I'd like to see merge fields be slightly easier to use, but you can still format everything really nicely in comments, so it isn't a big problem.,10,Saves time - Jira is easy to use and easy to learn, onboarding is a breeze.,,Slack, ChurnZero, OneNote,10,10I'm a fan!JIRA was used by our software development organization as the one true source for what work needed to be done, when and by whom. Although our approach was generally waterfall with some agile-esque concepts mixed in, JIRA proved to be a powerful tool for us. We created an extensive JIRA workflow to track and manage portions of our development projects from idea, design & requirements, development, QA, tech writing, UAT, etc. We also made extensive use of the dashboards to provide transparency to individual contributors and stakeholders alike.,The biggest impact from experience with JIRA is the transformation it took from when I first started using it, until now. It seemed like the good folks at JIRA really practiced what they preached and I reaped the benefits. When I first started using the agile boards, it was at a time when they had just come out with a new version if you will and were sunsetting the old version (I can't remember the names). Anyhow, the agile board worked enough for me to check the box that I had a backlog. It did the basics. As time went on however, I was thoroughly impressed at the features that they added. It was as if they had been sitting at my desk alongside me and noticing my frustrations and then fixing them. Other favorite features, dashboards, saved searches, workflow, labels, advanced search query, linked issues, follow issue, history, batch updates, view in issue navigator. All these features seriously make life easier when working in JIRA. The administrative headaches of product management are out the window. I also dig the administrative features like find my field. This makes it so easy for an administrator to identify the cause of a configuration error and fix/test quickly.,One thing that ever bothered me about JIRA was the rank feature. It used to be a global rank, so I could I query issues and display them in results by order of priority (rank) regardless of what sprint they were in. Now rank is only applicable in the context of a sprint, which is not so powerful really if I want to prioritize across several teams regardless of sprint. It would be nice to batch update labels, and not have the "all or nothing" approach. At least they have keyboard shortcuts that make updating many issues one at a time a total breeze. At my new company, I'm having a hard time converting my peers and management into JIRA admirers. Their concerns are mainly the price and the ease in which the system can be integrated into our homegrown system. Can you make some sort of browser plugin that could compare how long it takes me to complete the same work in JIRA vs my current application?,10,As a product manager I needed to make sure that all teams were aware of priority and that new items went through triage and were accounted for in a timely manner. JIRA took us away from the headache of spreadsheets and daily meetings, to one transparent system with real time dashboards that required no meetings. People could just do their work because they knew what was the next most important item. This must have saved hundreds of thousands of hours over the years.,,Balsamiq, Adobe Photoshop,keyboard shortcuts are amazing and same so much time Find my field is an amazing feature that also takes me to the correct admin config for me to make the updates I want so that I don't have to hunt around for what I'm looking for. The advanced search and saved searches make finding the issues important to me very easy. Nothing falls through the cracks.,Managing labels across the system can be tough. It can get ugly if you have a lot of people using them and one person uses a capitol and someone doesn't. Then your searches need to include all permutations of the label to make sure you get the results of issues you're looking for. Configuration can be a bit daunting, but the Atlassian university was a great help.,Yes, but I don't use it,9JIRA - Love at First Site for Developers, a Slow Courtship for BusinessThe use of JIRA is company-wide but sporadically. JIRA is viewed as an "opt-in" tool in our organization and is mainly sought by the development groups. We have had some success pushing it out to business users in departments that would benefit from ticketing and tracking of workload. In general, development and QA are the primary users.,Differentiated workflows. It was important to us that new product development could be handled differently than IT implementation bugs, etc., and JIRA does a great job of allowing us to treat efforts appropriately without a lot of complicating customization. Card view. The layout of the work items on the board is user friendly and easily gives the team a handle on what is happening during the working period. The drag and drop functionality is constantly lauded by our teams and whenever alternate tools are reviewed, is one of the top features used for comparison. Simplified Querying. One of the biggest selling points to the business groups that have taken on JIRA is that finding items in the system doesn't depend on someone with say, SQL talents. Though there are complaints on querying more complicated information from some, overall the WYSIWYG interface for querying tickets is very helpful for business users to "self-service" information. Integration with wiki tool (Confluence). This I think is one of the biggest draws for us on the business side. We find that JIRA is sometimes too complicated for the business user and were able to build dashboards and pages that help the business users navigate to what they need to know. Being able to maintain up-to-date reporting from JIRA without having to constantly update is beyond valuable.,Reporting. JIRA has always been a little finicky on the reporting side in my opinion. The gadgets are helpful but can be confusing if you aren't shown how to use them. Time tracking continues to get worse rather than better with the removal of the one built-in timesheet we had replaced by a paid plugin with fewer options. Roles Based Permissions. JIRA is really light on this but you can work it out using validations in the workflows and permission schemes. I think this is not intuitive for most admins and they wind up with a very unrestricted instance of the tool. Sometimes setup can be a pain because of the openness. Ramp up is long. JIRA is really difficult to understand and to be properly configured if it doesn’t suit you out of the box. Once you understand all the ins and outs of the setup process you can wind up with a decent tool but it's the fact that you need someone to sit there and learn it before you can use it - not a coherent message to management when pitching Agile. Or to some "missing features". Some features that the community feels should be a part of the core product are only available via plugin. Again, the message to management when trying to purchase these is disconcerting to leaders that are used to the "big box, all in one, everything you need, one price" solutions. Business Features. Depending on your final configuration you may find tracking business features rather onerous. Based on release structure we have a non-traditional setup where our business projects exist in one space with children work in software spaces. It is the easiest solution to our technical release issues. There is only one ticket type that can have children spanning projects and it is the Epic. Pulling in children tickets is time-consuming and laborious. I discovered that I could automate update of a ticket field on children tickets to help tracking back but it's not elegant and is open to creating gaps should things change (and they often do in Cloud JIRA).,8,Positive: this tool provides a convenient and efficient workspace for our developers/QAs as well as transparency for our leaders in the Dev/QA space. Higher level tracking (at the Epic) level gives greater transparency at the business feature level but could be improved. Negative: this tool requires a lot of time to learn and maintain. Updates are not always clear in their impact so you do accept (even in a Cloud situation) that if you do not use JIRA with no modifications (I have never heard of this by the way) you will need someone to keep an eye on it. Consider it to be 25% to 50% of a headcount based on your configuration complexity.,ServiceNow and Workfront,Atlassian Confluence, ServiceNow, MS SharePoint,No,8,Yes,None spring to mind at the time of this writing but I have very positive impressions of the support team at Atlassian.,Prioritization for Stories, etc is very nimble; caveat for the issuetype "Epic" which is decidedly less so. Sprint planning WYSIWYG query tool Dashboard gadgets for Agile development tracking,Feature prioritization (at the Epic level for our shop) is very hard to use in the Backlog - we've developed a hack where we prioritize Epics in a Kanban board but it's got an element of disconnect to the Backlog planning that isn't very "agile" Portfolio tracking - you might try to arrange features according to Business Goals but you'd have to 1) purchase the Portfolio tool from Atlassian which is the same price as the JIRA software itself or 2) build and maintain insane filters Time tracking - your time tracking will again be a choice between purchasing a plugin that does half of what you want or maintaining JQL that does backflips for the same level of value,Yes, but I don't use it,8Jira is great for what it's good at!Across all software development teams, we use Jira for work including: defects, stories, epics, dependency mapping, etc. Each team has their own Jira project and their own boards (Agile board or Kanban boards) and the projects in Jira are maintained by Project Leaders. Jira is heavily used by QA for defects and story verification. It is also used by analysts and product owners for story and requirement communication to development teams.,Tracking hierarchy and linking for Epics -> Stories -> Defects. Linking stories in one team's Jira project to another project, due to dependencies needed for enterprise software development. Flexibility in set up and workflows can vary by team, and can be customized by that team.,I'd love to be able to customize further what types of data shows in different views (e.g. Backlog vs. Agile Board). I'd like to see more data in the links between stories, as well, so that you can see more info without having to link out to the other story and view.,9,Jira is definitely quicker to learn and easier to use than a variety of other products that we've used, so the ease of adoption is great. I do wish it was easier to maintain certain information (priorities, previously scheduled/committed dates, etc.) - if it could do that, it would be more valuable to our organization. It's a great ROI that users can easily add images, videos, or other artifacts to the Jira items themselves.,7Atlassian JIRA has significantly improved our work intake and request tracking processesOur organization uses JIRA for work intake and tracking across multiple departments. It was initially implemented by our Software Development department to manage day-to-day support requests and bug fixes. However, it was so successful that nearly every other department has set up their own project(s) and developed new processes for managing their work intake, centered around JIRA. When used in conjunction with JIRA Agile (it used to be called GreenHopper), JIRA is a fantastic tool for identifying bottlenecks in the process. We use it for work intake, prioritization, tracking, and ultimately as a record of work completion.,Excellent for use as a repository for work requests Allows easy prioritization of work requests Can be highly customized to match your processes,The administrator tools can be difficult to understand - there is a pretty steep learning curve if you want to start customizing I wish you could attach a screenshot during issue creation - I don't know why it's available once the issue is created, but not as part of creation,10,Dramatically improved visibility into work queues across multiple departments Streamlined work hand off processes - e.g. software development can hand off code to quality assurance, who uses JIRA to track bugs, and can watch the progress of those bugs right in the tool I use both a hosted instance (for internal work tracking) and the cloud service (for work tracking with outside vendors) and both are fantastic,Asana,Basecamp,Zendesk,,,Managing day-to-day software development support requests Tracking work with outside vendors Managing configuration or support requests from sales staff,We use JIRA to track annual and mid-year performance reviews - every employee is a "ticket" and every ticket is assigned to the appropriate manager, who has to track their progress towards writing a review, reviewing it with the employee, and delivering a signed and finalized review to HR Many departments use JIRA to track internal work, so that everyone on their team knows the current status of any particular issue,We already use JIRA to track almost all of our work. I imagine that if additional departments are created, or new, novel projects are begun, JIRA will continue to be the go-to repository for work tracking,10,Implemented in-house,Change management was a big part of the implementation and was well-handled,10Atlassian JIRAAtlassian JIRA is used by some sections within the organisation. It is mainly used by IT for managing project work and workloads. It is also used to keep track of feature requests for a piece of software we have had externally developed for us. We are currently piloting the use of Service Desk for one of our business units.,Easy to use and configure. Provides visibility of workloads. Provides visibility and tracking of progress against certain tasks. Allows you to go back and track historical decisions. Good roadmap, existing and new features always being worked on.,Within the Agile area it would be nice to be able to track versions more easily, whilst it does it I don't find this area all that intuitive.,9,From an IT perspective this allows us to make sure we are managing workloads and due dates effectively. From an organisational perspective it provides us with a tool we can use to track issues and tasks, with minimal setup overheads and minimal training. It is also very configurable, allowing us to configure JIRA to match business processes rather than needing to change business processes to match JIRA.,10,Adding new issues Tracking progress and recording comments against an issue Assigning issues to employees so they are responsible,Yes, but I don't use it,10Useful tool, could be better at some thingsJira is used across the organization to compliment scrum practices. We use it for planning and tracking sprints, and managing backlogs.,Managing sprints is easy,A sprint notes report that could be easily formatted and exported would be very useful. A built-in way to roll up Epics to a higher program or strategic level would be useful. Being able to add reports to dashboards should be added. People who are not power users should be able to see information on the dashboard - all in one place. Dashboards are limited in usefulness because you cannot really show project status.,7,N/A,None,10,Creating stories Creating a dashboard,Searching based on assigned sprint Only 1 filter can be used per scrum board and you cannot adjust the view of the plan board Ensuring that the same fields are visible to edit when entering/editing a story is not straightforward. Does it have to be customized in multiple places?,7
Unspecified
JIRA Software
1459 Ratings
Score 8.1 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>TRScore

JIRA Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
JIRA
1459 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.1 out of 101

Do you work for this company?

TrustRadius Top Rated for 2019
Show Filters 
Hide Filters 
Showing 25 of 1460 JIRA ratings and reviews.
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-25 of 25)

Companies can't remove reviews or game the system. Here's why.
Elissa Bernstein profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Usability

7
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Read Elissa Bernstein's full review
Kyle Kochtan profile photo
Score 5 out of 10
Vetted Review
Verified User
Review Source

Usability

4
JIRA's UI is very difficult to navigate. It is almost impossible to find things. I find myself just using the address bar and putting in the ID numbers as I can't find what I need anywhere else. There is no one place to do tasks but many and many ways to get there and this causes confusion.
Read Kyle Kochtan's full review
Harry Miller profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Usability

8
The initial configuration of Jira can take considerable time, once the settings are configured, using the tool is very simple. Creating tasks, starting reports and evaluating project progress is easy and fast. It allows the user to create and edit attachments and screenshots at a click. It integrates with other applications used by the project is simple.
Read Harry Miller's full review
Tory Trone profile photo
August 14, 2019

JIRA works

Score 8 out of 10
Vetted Review
Verified User
Review Source

Usability

8
JIRA does everything you need but has a steep learning curve. JIRA also a somewhat difficult user interface. It takes some getting used to. However, everything you need to have a fully working and customizable project management software system is in place for you to use. I still prefer it to many other PM software solutions out there.
Read Tory Trone's full review
Viktor Mulac profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

9
Great tool for 'easy' tasks like recording and tracking user or customer interactions. A key for success is that all team members use it and update it regularly. In the SW development, JIRA can be connected to GitHub and gets more details about virtually each commitment a developer makes so a manager using JIRA is able to put an individual performance in the context of the quality of software work products.
Read Viktor Mulac's full review
Cristian Bodnarasec profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

9
JIRA user interface is easy to use and provides a nice user experience. Its integration with the other Atlassian tools like Confluence, Bamboo and Bitbucket makes it the one place to go for your project management/bug tracking needs.
For JIRA administrators like myself, it takes a while until they learn everything especially when they need to address complex requirements for different departments.
Read Cristian Bodnarasec's full review
Shoba Sharat profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

10
Even novice users can easily learn to use JIRA in our organization. It is not complex to understand the workflows designed for product development. Administration and security management has been easy with complete data protection.
Read Shoba Sharat's full review
Tom Young profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Usability

9
Jira has so many options that you actually find it pretty complex. It is this kind of applications where you accept the high learning curve and actually enjoy learning everything and becoming a wizard. So the overall usability is good. You can scale up and down and find what suit your needs bets or even the individual projects.
Read Tom Young's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

10
Very structured in that once you learn all of the bells and whistles, you can easily manage 100 projects concurrently. Sprints can easily be adjusted, backlogged tasks pulled forward or tasks moved out. Auto notifications (once setup) will drive the development process so that hand holding is kept to a minimum.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Usability

7
It is not the ideal user interface for managing information but that could be managed by your JIRA administrator. It does have a wonderful interface to other project management tools such as Aha, ProductPlan, etc. I would suggest that product management and R&D work closely with the administrator to ensure that the look and feel maps to the company processes.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

9
JIRA gets a 9 out of 10 for the visual component, as it could be better
looking but is very functional. It meets all of our needs, with room to grow as
our projects and resources expand into the future. It has some customizable options
for reporting and tracking that help us draw out the info we need to be
successful as project managers. JIRA is a great tool for partnering with IT and Finance
to account for resource use and expenses.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Usability

10
Editing fields almost everywhere works in place, attaching images and files works with drag and drop or copy and paste. Personally, creating advanced filters is the killer feature for me. You can point and click, and at one point you are allowed to enter and modify the query in the JIRA query language, which makes adoptions very easy and concise.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source

Usability

9
It is versatile and has many features and customization tools with a lot of filters and components that are easy to implement. Project management and issue tracking are very easy with workflows, dashboards and custom reports. It can be integrated into version control tools to check the configuration items before committing. Provides change management needs without any major bugs or fails.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Usability

8
I think JIRA has a lot of complexity for a less technical user and I am torn between whether that is an essential problem. I tend to believe that users should choose the tool that fits the work; this means does it make sense for the typical user and how much integration with other systems does it provide? If both of these things are high, I would say the tool deserves high consideration. As a technical tool I think JIRA falls squarely in line with technical expectations - it also provides a high degree of integration possibilities with other tools. I suppose if you were forced to choose one tool you should plan on a staggered approach to rolling it out, starting with the technical team guided by someone with a process background.
Read this authenticated review
No photo available
October 06, 2014

Atlassian JIRA

Score 9 out of 10
Vetted Review
Verified User
Review Source

Usability

10
In our experience users have required little or no training to get up and running with this product.
Read this authenticated review

About JIRA

Atlassian Jira is a task management tool for software development teams developed by Atlassian in San Francisco. Atlassian Cloud and local server options are both available. It allows the user to create, prioritize and track the progress of tasks across multiple team members. Projects are treated as and formed from, in this software, collections of issues, which can be managed individually or in bulk in a multitude of ways. Analytic features allow team member workload and time to resolve issues to be studied and reallocated as needed. Issue voting allows team members to up or down prioritize elements of a job. Tasks can be delegated and issues can be started anonymously, if need be. Customizability and functionality are extended via extensive support for plugins. Pricing is dependent upon inclusion of Atlassian Agile (for development) or Atlassian Service Desk and upon the number of users, in both cloud or local server options.

JIRA Integrations

SnapEngage, Freshservice, Stackify Retrace, Planview PPM Pro (formerly Innotas)

JIRA Competitors

Pricing

Has featureFree Trial Available?Yes
Does not have featureFree or Freemium Version Available?No
Does not have featurePremium Consulting/Integration Services Available?No
Entry-level set up fee?No

JIRA Technical Details

Operating Systems: Unspecified
Mobile Application:No