Jira Reviews

We are using Jira for scrum, specifically for Agile Scrum. Most of the tasks are in Jira, including the dashboards and reports.

For now, we are using Jira for the scrum. We are quite happy with this as it allows for task management and report generation.

We can query the tickets and create dashboards based on these queries. This functionality is helpful for monitoring project status and tracking bugs. We are using Jira for scrum within the Agile framework. Tasks and dashboards are in Jira, which also assists in report generation.

I am unable to query based on the subtask and link by issue, which can be improved.

I have been using Jira for more than five years because my previous company also used it.

For stability, I would rate Jira as eight out of ten.

For scalability, I would rate Jira as seven out of ten.

I have not contacted Atlassian's technical support since another team handles these issues.

Positive

I have tried Trello, which is open-source and free, however, Jira is much more powerful.

The setup of the project in Jira is handled by our scrum master, who is not a very technical person, yet manages it efficiently.

For small companies, Jira is not affordable, leading them to use Trello or other free software. Jira is quite acceptable for medium to enterprise-level companies due to the features it offers compared to its pricing.

I have not used Asana, but I have used Trello. I find Jira to be much more powerful.

Overall, I rate Jira eight out of ten. I am quite content with its features and capabilities.

My company doesn't use Jira for service desk management. My organization uses Jira in areas like user stories, ticket tracking for work, dashboards, and kanban boards.

The product has improved my organization since it provides a common point of reference for tracking work from different groups, including developers, QAs, and project management areas.

The most valuable feature of the solution is the ease of replication of tickets.

The documentation on how to create dashboards and take advantage of other features in the tool are areas where the tool has certain shortcomings. The tool needs to have documentation on how to take advantage of different features in general.

In the future, I would like the tool to provide better integration with other tools. My company uses BMC Remedy. Integration of Jira with BMC Remedy, which is our company's ITSM tool or support tool, would be helpful. Better integration with other tools is required. I work in a large organization, where switching tools is not a rapid process owing to which getting data from one tool to another can be a cumbersome process.

I have been using Jira for four to five years. I don't remember the version of the solution. It is a tool that is configured at multiple places, so you can use it in one place, and it looks totally different in the next place, even though it may be based on the same version. I use the tool's current version.

Scalability-wise, I rate the solution a nine out of ten. It has scaled up well to meet the needs of a large number of users in different roles in our company. There are some complexities that make it a difficult tool to use. Better integration features would help with the tool's scalability.

Around 1,000 people use the tool in my company.

I received technical support from my company's internal tech team.

I have experience with some other products.

I did not take care of the product's initial setup phase, but I know it is a complex process.

The solution is deployed on an on-premises model.

I rate the tool a nine out of ten.

The solution is used for project management and agile software development. It is also used for general business planning. We can use it for any small or large project. The tool is designed to do sprints and Kanban. It was built for Agile. It works well for any Agile-style project.

There are various versions of Jira. Help desk process, using ITIL, planning a new product from scratch, marketing, task management, and team management can be done in Jira. We use automatic print preview settings and visualization of the progress. We can link all of our information in Jira into Confluence to do live meetings with live data. We have a lot of templates in Confluence for any business or team meeting we need.

The reporting and analytics features make it easy to calculate team velocity. We can track time and effort. It's very easy to generate burn-down and burn-up charts for Agile teams. It also has many useful automatic charts for help desk services. I haven’t used it much, though. We can integrate a lot of tools with the solution.

A lot of companies use a mix of Waterfall and Agile methodologies. They often need more individual metrics for time and cost tracking. Many larger companies would like to have more resource management within Jira. The model for adding features is by application. If we add an application to Jira, we must pay for the licenses for everybody on our contract when only a few people need to use the application. Adding applications is very expensive. We cannot make it for only the few users that need it. We must buy the application for the entire workforce that's using Jira, so it's not very flexible.

I have been using the solution for three or four years.

Overall, the product is stable, but it has had some security problems and a major outage in the last couple of years. It's something to be aware of, but I don't worry about it that much.

The product’s scalability is pretty amazing. I've seen customers with over 10,000 users, and it works well. I don't have a lot of scaling needs. However, it's super easy to onboard new people. And I've never had to worry about running into performance problems. We just add the people, and it works.

If we are starting a project with a small team from scratch, we can have Jira up and running in about ten minutes. The deployment process is logging on, adding the users, and hitting the start button. It's very easy. The tool is deployed on the cloud. I recommend the cloud. It is usually better and the easiest.

The ROI is excellent for the cost of the basic product. It has so many features and integrates with so many things. There are a lot of useful free apps available. We can really improve our project management and task management at a low price compared to buying a bunch of other products. It's very flexible. We can adapt it to different kinds of projects. We can adapt it to the way the teams need to do the work instead of having to learn the rules of the software itself.

I use a monthly subscription. We can opt for an annual subscription if we go through a reseller.

I tried Asana and Trello. I chose Jira because it integrates with many other applications and easily expands with its own apps. The integration within the Jira, Confluence, and Atlassian products is automatic. We don't have to spend time linking information and data. We just need to install it, and it will be ready to go.

I haven't used a lot of direct integration with Jira. I've seen it used with code repositories for continuous integration and continuous deployment. It's really fast. Everything is automated and very easy to set up. I haven't used all of the features. I would definitely recommend Jira. My advice is to use the online resources on the Jira home page. There are a lot of people who will help you set it up for free. We can avoid making a lot of mistakes by using the community advice. Overall, I rate the solution a nine out of ten.

We are using Jira to plan and manage projects, including tasks, sprints, and releases.

It allows teams to create, assign, and track issues. It supports various agile methodologies like Scrum and Kanban, providing tools for backlog management, sprint planning, and burndown charts. 

It offers robust reporting capabilities, allowing teams to track progress, monitor team performance, and generate visual reports.

Jira's user-specific dashboards and reporting capabilities provided insights into individual and team performance. This promoted accountability and allowed our development team to recognize and reward high-performing team members.

Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication. Teams can discuss tasks, provide feedback, and track progress in one centralized platform, leading to smoother workflows. 

Tracking bugs, feature requests, and development tasks was cumbersome. It was difficult to prioritize and assign issues, leading to delays in issue resolution. With Jira's issue-tracking capabilities, we can create customizable workflows. This enables users to capture, categorize, and assign issues with ease. As a result, the development team can address issues promptly, improving product quality.

Jira's native support for agile practices, including Scrum and Kanban boards, allowed our development team to embrace agile methodologies seamlessly. This enabled them to prioritize features, plan sprints, and adapt to evolving client needs more effectively.            

Jira's user-specific dashboards and reporting capabilities provided insights into individual and team performance. This promoted accountability and allowed our development team to recognize and reward high-performing team members.

Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects.                            

The high level of customization and feature-rich nature of Jira are confusing for new users, requiring some time to learn and navigate.

Administering Jira, especially in large organizations with complex workflows, can be challenging and may require expertise.

I have been using Jira for issue tracking and task management for the last seven years.

We did not previously use a different solution.

We use the solution for secure software development. Additionally, we use the service-based system.

If our software factory delivers, individuals will need to provide instructions on how to use the software factory.

The integration is nice. We can integrate with TeamViewer and many more solutions. We need to go into Jira to complete the secure software delivery.

The solution could be cheaper.

I have been using Jira for ten years. We are using the cloud version of the solution.

The product is very stable.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is good.

100 users are using this solution.

I rate the solution’s scalability a seven out of ten.

Jira is providing all information.

Positive

Migrating from an old server agent is quite complicated.

We have a very small organisation. Two IT people are needed for the solution’s deployment.

I rate the initial setup a six out of ten, where one is difficult, and ten is easy.

The product is quite expensive. It costs approximately 1.2 million rand per year.

It's a fixed price, depending on the modules that you get. You have specific tools, that's what you pay for.

I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.

I would advise people to use Jira. There are other open-source products available that individuals can consider first, depending on the company's budget. Jira is a fairly stable product, but there are other open-source solutions worth exploring.

Overall, I rate the solution a seven out of ten.

I use Jira for maintaining our user stories, creating defects, and tracking progress. It's a part of my daily workflow. We have a dashboard where we manage stories within sprints, see backlog items, and keep track of both open and closed defects.

Jira facilitates bug tracking in our projects. When we find a defect, we log it in Jira and assign it to a developer. Once the developer fixes it, the defect moves into verification or the QA stage. The QA team validates the fix, and if everything is good, they close the defect. If needed, they can re-assign it back to me with comments.

I like how easy it is to collaborate. We can add comments and tag specific people, which is useful for both onshore and offshore teams. Here, we can tag the person easily, and Jira updates. The commenting feature keeps everyone updated on what work has been done. Jira has a lot of versatility, which makes it a handy tool.

Within Jira, we can tag stories by the current sprint and associate them with the developer working on them. We also use Jira to track story points and progress based on status. Once a story is ready for QA, the QA team can create sub-tasks directly in Jira and start their work. 

So, Jira is great for story management, but I'd like to see better tracking of employees' daily status for improved visibility for higher-level stakeholders.

The communication features could be enhanced. While Jira sends email notifications when comments are added, it would be great to have a more real-time chat function directly within the Jira dashboard. This would streamline communication when we need to clarify defects.

Also, test case management could be more user-friendly. When we add or update test cases, there should be a better way to organize them within the dashboard.

I've been using Jira for over seven, maybe eight years now.

I haven't experienced any stability problems myself, but there's always room for improvement. So, I would rate the stability an eight out of ten. I have not faced any major issues with Jira's stability.

I would rate the scalability an eight out of ten.

Everyone uses Jira. If something isn't working, that person likely isn't working either.

I've always worked with Jira since the beginning. It is a tool 

The initial setup of Jira is relatively straightforward.

Overall, I would rate the solution a seven out of ten.

I would recommend using it. It's the only tool where everyone can work within a single system, and we can track each other's records. That's a tool that helps people stay aligned.

I use Jira to schedule tasks, customize them, and track progress within sprints. We follow a two-week sprint structure and manage all our tasks within Jira accordingly. We use it in the defense industry, and our applications are related to satellite communication. 

I have experience with Jira's bulk tracking and issue management. We use it to add new features to our product, fix bugs, and address customer feedback.

The features I find most valuable for work and team productivity are creating subtasks and tracking their completion. Additionally, reporting features such as burnout charts and task reporting are quite valuable for us. 

The tool's integration capabilities with other tools are quite nice. It's an open tool that easily integrates with third-party products like Microsoft Project and GitHub. Integrations work smoothly; we've also integrated it with requirement management tools per our needs.

Improvements in Jira for the next release could include adding AI tools for dashboarding, making it easier to report insights, and enhancing business intelligence capabilities. It should also improve on-prem support. 
As far as I know, Jira's on-premise support is being discontinued. From last year onward, they stopped providing on-premise licenses and now only offer cloud support. This shift happened gradually, and I believe they now only offer cloud licenses.

I have been working with the product for ten years, since 2014. 

My company has 200 users, of which nine to 10 are from my team. 

The documentation and the internet are enough to clear our doubts. 

Positive

The tool's deployment is easy; I rate it a nine out of ten. It can be completed in two to three days. 

The tool's pricing is expensive. The new pricing is indeed quite expensive compared to what it was a few years ago. Last year, when we intended to renew our subscription, we found the pricing considerably higher.

The decision to use Jira on-premise instead of the cloud is primarily driven by security concerns, especially in industries like defense, where sensitive information must be protected.

We want to continue using the tool, but we may have to explore other options due to the lack of on-premise support and Atlassian's emphasis on cloud deployment. If it extends its support for on-premise usage in closed network environments, we would gladly continue using it, considering our current investment and experience with the platform. However, if no such support is provided, we may need to evaluate alternative solutions that can be deployed on-premise.

I recommend using Jira because it's easy to work with and open, allowing for integration and development of additional features if needed. Its ecosystem is vast, with a large community worldwide using Jira, and it offers many add-on products for various needs.

I rate the overall product an eight out of ten. 

We use Jira for ticketing purposes, project management, and writing stories, epics, and milestones.

The solution's maintainability, user-friendliness, and learning curve are all very good. We can use the solution's queries to filter everything and get the data out for business processes. Jira queries can be used for different types of deployment automation processes.

The solution should be more user-friendly and include integration with different tools.

I rate the solution a seven to eight out of ten for stability.

The solution’s scalability needs improvement. Around 5,000 users are using Jira in our organization.

The solution’s technical support is quite good.

We previously used ServiceNow. We switched to Jira because it is more user-friendly and an easy-to-use tool for project tracking, project management, and integration. Compared to ServiceNow, Jira is easy to maintain.

The initial setup of the solution is quite complex and should be simplified.

We have seen a 90% return on investment with Jira.

We use Jira for sprint planning and agile project management. We used to maintain a two- or three-week sprint. We found and tracked different user stories, epics, and milestones in that sprint. We used to complete the two-week sprint with all the user stories, epics, and milestones in that particular sprint. We also put the blockers we use in the backlogs so that they could be handled in the next sprint.

Jira's bug tracking and issue resolution works quite well. Users should explore more features and understand and learn more about the solution.

Overall, I rate the solution a seven out of ten.