Jira Reviews

We follow an Agile framework and use Jira for sprint planning and management.

The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task.

It offers very good APIs for creating custom integrations and has many built-in integrations with other tools.

The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement. 

I've been using Jira for about three years.

The platform is very stable. I haven't faced any stability issues with it.

Approximately 70 to 80 people are using Jira in our organization. It is a scalable product. 

Setting up Jira takes some time. You need to create dashboards, configure settings, and test those configurations. The default setup is straightforward, but understanding and applying the various configurations can be time-consuming.

For smaller organizations, it might be better to consider alternatives like Linear.io. But if you need an integrated system, especially with other Atlassian products, Jira is a solid choice.

It is widely used, so the transition is easier if someone moves from one organization to another that also uses it. Additionally, its automation features are powerful and can address many use cases.

The reports are useful, giving an overview of a sprint's progress and indicating areas for improvement. However, I have yet to use the analytics feature much.

I rate it a seven out of ten. 

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.

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.

I use Jira for project management. 

Jira is designed for issue tracking, making the process much easier than traditional methods like paper-based tracking. It is number one for agile management.

Jira's reporting and analytics features provide a clear picture of what happens, making them good. I use it in my work. 

The tool should improve its pricing. 

I have been using the product since 2006. 

The solution is very stable. I rate it a nine out of ten. 

I would rate the scalability as a ten out of ten. It's highly scalable, accommodating from just a few people to potentially several thousand without issues.

I've encountered delays and found that some of the responses from technical support weren't very helpful in resolving issues.

Neutral

We switched to Jira because it was better regarding features and execution. 

Setting up on Windows is very easy, while on Linux, it's a bit more complicated. I would rate it around a seven out of ten. It is possible to deploy it both on the cloud and on-premises. The deployment duration varied based on whether it was on the cloud or a server. If it was on the cloud, it took slightly less time, while installing it on a server took anywhere from ten minutes to an hour. 

I installed the product myself. 

I recommend Jira because it's the best tool for project management, issue tracking, and support. I rate it a nine out of ten. 

In our organization, we use Jira for project management and usually use the Scrum project type. We might adjust the workflows and stages to better suit our needs, but we mostly use the default functionalities it offers to manage our projects.

It's flexible and customizable, and we frequently use it with customized workflows and dashboards to track defects. Jira works well with tools like TestRail and Clarity, which help with test management. It has various APIs.

Jira's reporting and analytics features support project management by providing useful out-of-the-box reports. These include burn-down charts for Agile project management and various other reports. These default reports typically cover around 60 percent of users' needs. Users can customize their reports and dashboards for the remaining needs, which usually fulfill about 80-85 percent of requirements. Add-ons can be used for the remaining small gap.

The tool mainly supports remote or distributed team collaboration through its cloud version, accessible from anywhere. Within Jira, you can communicate effectively with team members by assigning issues, leaving comments, and referencing people for notifications. While direct communication features within the tool are decent but not outstanding, integration with tools like Slack or Teams can enhance collaboration further.

Jira could be easier to use, especially for administrative tasks. It's quite complex, so it's important to understand it well. While the reporting and dashboards are good, there's room for improvement in some areas where extra features would be helpful.

Sometimes, we need add-ons in the product, especially for reporting. While you can get these through add-ons, they can be pricey. The licensing system for add-ons might also seem unfair because you often have to pay for all users, even if only a few use the add-on. So, maybe the licensing model could be adjusted.

I have been working with the product for ten years. 

I rate the tool's stability a nine out of ten. 

We've never had any issues, even with up to 2000 users. However, scalability can be limited by the license type. I'd rate Jira's scalability as a ten out of ten.

The tool's support is helpful. 

Positive

For deployment, setting up the tool takes minutes. Implementing additional configurations like SSO or integrations might take half a day to a day. The time spent configuring and customizing screens and workflows depends on your specific needs. I usually take about three or four days to complete everything.

The licensing cost for Jira is typically around seven dollars per user, though it may vary depending on regional variations. This cost is for a subscription-based model rather than a one-time purchase. I rate its pricing a seven out of ten. 

I work across multiple projects, so people might approach me for support when needed. I would recommend Jira to other organizations. For inexperienced users, I would advise seeking help from experts if there's something you can't do in the tool. They can customize it to fit your needs. Overall, I'd rate the product an eight 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 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.

We use Jira for various purposes. Firstly, we use it to gather requirements by raising tickets and tracking them in the system. Additionally, we utilize it for bug-tracking. 

What I really like about Jira is that it ticks off all the boxes for any agile project. It's easy to set up, easy to use, and it has excellent notification features. Jira is the top choice for anyone working on agile projects like ours.

The tool lacks support for testing aspects, which means we often rely on integrations with other tools for testing purposes. If Jira could incorporate testing modules within its platform, it would eliminate the need for external integrations.

I have been working with the product for five years. 

I rate the tool's stability an eight out of ten. 

Jira is scalable. I rate it an eight out of ten; we have nearly 100 users. 

Installing Jira isn't difficult, but our administrator or IT help usually handles it, so I'm not directly involved in the installation process. We have around 50 resources for deployment and maintenance. 

Jira is worth the money. 

I rate the tool's pricing a five out of ten. It's paid yearly. 

My advice would be to explore the different licensing options available for Jira. There's a level of customization in pricing to tailor it to your needs. I rate it a ten out of ten.