Jira Reviews

Our primary use case for JIRA is for project tracking to see where our development team productivity is.

This product has been very helpful for me in terms of creating tasks and tracking my development team's productivity. 

I think support could be improved, in particular it would be helpful having a login for the support team.

I've been using this solution for six years. 

This solution is very stable.

This solution is scalable. 

It was easy to deploy this locally, I'm not sure if it would be the same at enterprise level. We have nearly 300 users in the company. 

I've tried some other solutions including Plenty, ClickUp and Azure. I feel that Jira is far better than these other solutions. 

I would recommend this product for people who have agility.

I rate this solution an eight out of 10. 

The timeline management is great and the dashboard allows me to see the performance of everyone working for the company.

The filtration could be better.

I have been using Jira for six months.

Stability-wise, it's not the best, but it's stable.

Jira is very easy to expand upon and customize.

The initial setup was very easy. It's a very user-friendly solution but sadly, deployment for Jira is not the best.

I would highly recommend Jira to other interested companies.

On a scale from one to ten, I would give Jira a rating of eight.

We use Jira strategic management and overall best practices management.

Jira is easy to use and there are a lot of tools that are integrated with it.

The solution can improve by including test management functionality in a native bundle without plugins.

I have been using Jira for several years.

I have found Jira to be stable.

Jira is scalable.

We have approximately 50 users using this solution in my organization.

I have not used technical support.

The initial setup is simple.

We had our internal IT team that did the implementation and we do not require maintenance.

We are on an annual license to use Jira.

I evaluated other options. I choose Jira to work with because it is a popular solution and many of our customers use it.

I rate Jira an eight out of ten.

Public Cloud

Large user base. Great for tracking defects but that's not really all it can do. It is used for tracking "issues" in general. Issues can include Defects, Change Requests, Requirements, User Stories (Agile), Sprint Planning (Agile), Progress Tracking, etc. The pricing is also excellent and they offer flexible subscription plans. Great technical support being a commercial product. Quite stable as hardly seen any downtime in the few years I've used it in different companies.

The workflow and layout can be confusing and takes a while to get used to.

We using this solution to handling all of our development and support tickets.

We have found the structure, functionality, and how Jira handles the tickets most valuable.

The performance could be improved in the future.

I have been using this solution for approximately four years.

We have had some issues with stability.

The scalability is good for what we are using it for. We have approximately 20 people using the solution in my organization and we plan to increase usage.

The technical support could be more responsive.

We have one technician handling the deployment of Jira in my organization.

There is a monthly license required for this solution and it is expensive.

I would recommend this solution to others.

I rate Jira an eight out of ten.

Public Cloud

Our primary use cases for this product are project management, customer relationship management, internal management, and collaboration.

It's an open API. We also have the best community to support any problems that we have.

Cost could be improved. The pricing is quite high. I could also see there being a need for improvements in software product management, project planning, and DevOps. 

I have been using Jira for six years. 

It is stable. 

The product is used on a daily basis by 2,000 people. However, it is not easy to scale. 

Technical support could be made more efficient and localized. 

The initial setup was somewhere in the middle. Not very simple; not very complex. 

We worked with consultants and deployment took us two months. All maintenance has been handled by vendors from outside of the organization. 

Public Cloud

Amazon Web Services (AWS)

We used JIRA for:

• Writing down requirements and stories.
• Analysis
• Creating tasks, subtasks, and defects.

It also helped tracking the sprint process more efficiently.

It gave us control over all test artifacts in one place, along with easy traceability, mapping between stories, bugs, test cases, and test cycles.

The traceability mapping feature is something that became very useful, especially during releases and bug fixes.

The creation of epics and stories/defects is also very useful and simple.

It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins.

One to three years.

JIRA is the project management system in my company. We use it on a daily basis. It is the main instrument widely used by QAs, Product Developers, Technical Writers, and Project Managers

All issues are stored in one place. JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified. Also, JIRA is very customizable, for example, you can add unique fields or remove the existing ones. Reports, analytics, and a ton of widgets, they are great and intuitive. Perfect for an agile team.

1. History of changes/activities
2. Customizable path of changing statuses of issues
3. Ability to limit access rights
4. Integration with other tools

As a Technical Writer, I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA.

Three to five years.