Jira Reviews

I use it for portfolio countdown. I work as an enterprise architect in the company, and my usage of Jira is minimal. Software engineers in our company use Jira very heavily, but I do not use it for my day-to-day work.

Cadence management has improved with Jira bots.

Its visual display and ease of use are most valuable.

Sometimes, the status change is too difficult. The change of status is not configured correctly. We sometimes have a limitation on the number of changes that each workflow can do, so we get very restricted with the changes, and status change gets difficult. It could be specific to our implementation. 

Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done.

Color codes are currently missing in Jira. It is very limited in that aspect. I would like to be able to color certain impediments or features in red. I don't want to look at everything ticket by ticket. I just want to be able to look at the colors and see where we are. I am not getting that in Jira currently. Maybe it is there, and I don't know about it.

It is stable.

Once we moved to the cloud, it became better. Its scalability should be good.

We have more than 2,000 users. It is extensively used, and we want to use it more and more.

We never had a similar solution because we were a waterfall organization. After we moved to the Agile methodology, we started using Jira.

I was not a part of its implementation.

We most probably didn't evaluate other solutions. For Portfolio for Jira, we considered other solutions such as Planview or ServiceNow, but for the software engineering development life cycle, we probably didn't evaluate anything.

When we cut over to Agile, it was a huge task to get everybody on the same page in terms of the setup and rollout. When we looked at each other's desktops, it looked so different, and our central team did a lot of effort in making it all look the same. I saw the full central team being pulled forward to resolve these inconsistencies. 

It is so open that it allows inconsistency. So, you need to have a very strong and resourced team for the initial setup, implementation, and training. Otherwise, it can just fail. It could be a good thing that it is open, and everybody can have their own Jira, but finally, when the organization wants some statistics on what's happening at the enterprise level, you will not get any data. So, my suggestion to anyone cutting over to Jira is to have a very strong and resourced team centrally. You should roll out, learn, and come back to it. You should repeat this process and keep on learning and coming back. It has to be a very strong cycle.

I would rate it an eight out of 10.

We use Jira as a help desk, an IDSM. We use it on a daily basis. Every ticket gets opened on it.

It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user.

It's a very customizable solution, but as a customer, we're always looking for additional customization. There could be better customization in future releases. If we changed from Atlassian to another product, we would look for a customizable solution.

I have been using this solution for many years.

The stability of Jira is good. We haven't had any issues with stability or performance.

It's a license-based software, so if you pay more for the license, the solution becomes more scalable.

Customer support is usually good. I have had no issues with them. 

Setup was straightforward. There is no dedicated team for maintenance. Our IT department handles that. It's a simple solution.

There are no additional costs to the standard licensing.

I would rate this solution 10 out of 10. I recommend Jira. For the time being, everything is good. Their support is good. The platform is good. There are no issues with them on any level. We mainly picked Jira because of its stability, integration, and price. If a solution is well integrated in our environment, and it's not costly, why not configure it?

The biggest thing I have taken away from working with Jira is that it's very simple.

We are using Jira for requirement and defect management. Not for DevOps purposes, only application development.

The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features. Additionally, it is user-friendly.

The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again.

In an upcoming release, they should improve the user management features. For example, when I want to monitor a project as a CEO I do not want all the details but enough that I can understand. Additionally, these features should be accessible to me by mobile.

I have been using Jira for approximately two years.

Jira is a reliable solution for that medium-sized organizations. It's not for enterprise-level organizations, they have a long way to go.

The scalability has to be improved more because Jira currently is similar to a standalone solution with very limited integration. The integration with other products has to be more.

We have approximately 50,000 people using the solution.

We use our own IT department for the technical support of Jira.

The initial setup was complex.

We used to be on a perpetual license provided by our clients.

I would recommend this solution to others. Any new startup company can start with Jira immediately because it is now offered in the cloud.

I rate Jira a nine out of ten.

As a lead consultant, I assess the testing maturity and suggest how our clients can improve what they're doing. I also carry out training sessions for Jira and other solutions as to how they can effectively use the solution. 

I like the ease with which we can do our workflow administration, especially with respect to defects. We can do good work with the boards, whether it's a Kanban or a Scrum board. It's much easier with Jira than with other tools. 

The solution could be improved with respect to how the end-to-end is managed from product backlog creation until test completion. Although it can be customized, if there was a standard out-of-view box feature or a workflow, that would be helpful. There are features that are currently not out of the box and lack end-to-end traceability, such as the business value of a particular feature. It would be great if that were included. 

I've been using this solution for over two and a half years. 

The product is stable. 

We are currently working with an enterprise client and we are able to scale easily. 

Jira's technical support is good. 

I previously used HP ALM, as well as TestRail, which is now focused more on test management. ALM was the major tool that I used before we started using Jira.

The licensing costs are reasonable. 

This tool has good capabilities but you really need to know what you want to do and freeze down your requirements before using it. It can be challenging when people don't understand the difference between Kanban and Scrum, and how you use those boards effectively. 

I rate this solution eight out of 10. 

We are using Jira Interview to handle all the facts from clients and schedule calls with them. We have a different operations department that configures Jira, and we have technical people that help us choose the deployment model. 

The main reason we are using Jira at this time is for a different dashboard and chart. The major one that we are using is for the stock analysis, and it's nice to get that time log for our team, get the score of the game, 40 points delivered in a week or a month. we are using Jira for following purposes:

Issue tracking
Customizable workflows
Estimation & work logging
Progress reporting
Scrum boards
Kanban boards
Project-level permissions
Project backlogs
Email notifications
Roadmaps

Productivity increased by using this tool and organization can measure the productivity of a resource. early alert being displayed in the case of project failure and success. Org can identified the work load on resources for a day. 

We like the test cases in Jira. The orange dash items view was great, and we like the features and layout of the data. It's quite different, and people are now getting their items so quickly. We love the bulk edit feature. Jira also integrates well with Bitbucket.

Sometimes it takes time to load the data.

I've been using Jira since 2015.

Performance-wise, Jira is good, but sometimes it takes time to load that data. 

Jira is scalable. We have about 470 people working with Jira in our company.

The support team is very helpful and supportive. I requested multiple things and faced some concerns, they were very cooperative and responsive.

Asana. Jira has better work flow and features relative smart and easy to use.

It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. We have also build the custom workflows for the custom templates.  We use templates for our daily progress.

I would tell potential users that they should all get it.

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

We use Jira for enterprise planning.

We like team collaboration and cross-functional collaboration.

The history with Jira is that it is a bit complex for many users.

There are too many features.

The user interface is complex.

I have been working with Jira for five years.

We are migrating to the latest version.

Jira is pretty stable.

It is scalable enough.

We have 1,000 users in our organization who are using Jira.

We plan to increase our usage.

Before Jira, we did not use any other solutions.

The initial setup is straightforward, nothing out of the norm.

We had a perpetual license but have changed to a subscription.

We are not satisfied with the pricing. It has become more expensive.

We would prefer it to be cheaper.

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

I would rate Jira an eight out of ten.

We are using it for service management, change management, project management, and tracking the changes.

It is user-friendly, and you can manage your project according to the methodology you want. It is also easy to configure.

The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough.

So far, I've only used the project management parts. We are examining resource planning and sample plugins for the product. From my point of view, resource planning is a little bit hard to link with project management. Sample plugins are another part of the system, and we need to link it with project management in the BigPicture screen, which is a little bit hard. It would be valuable for us if we can do resource planning in BigPicture as well. Currently, it is another plugin, and you can only plan based on the people and not projects, and you cannot link it, as far as I know.

My company has been using it since the beginning of this year. It has been around six months. I have been using it for three weeks.

It is stable, and everyone generally looks satisfied.

We are trying to settle the project management part and widen it to all countries in our company. There will be many users.

We are working with a consulting company. Technically, we are okay because all of us are using it now, and there is no problem. We just need to see more details of some of the modules of Jira.

For its implementation and deployment, they have been working for one year.

Jira is a big platform, and you can use staff management, project management, and other fields that all companies want to use. If you use Jira, you will see the whole IT governance in one system.

With this solution, we can see the full picture in detail, but it can be improved. Resource planning is not easy for our project base.

I would rate Jira a seven out of 10. It will be an eight in the future. I need more time to work on Jira.

We use this solution because it comes with some of the products that we are using. It is a part of the package. Our usage is quite basic, and we have not finished exploring and deploying the whole solution.

It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer.

Based on the feedback from my admin, it is sometimes difficult to find some of the features. It is not a big deal, but its configuration interface can be improved to make it easy to find things.

I have been using this solution for three years.

It is very stable.

We have not deployed it on a very large scale. For now, we have ten users, and it is mostly used for our internal things, but from next week, we're opening it for the community. We'll have a broader experience of the product.

We haven't used their technical support so far.

I have not heard of any complaints about the installation. It takes almost half a day to install. It took some time to configure it for different tools that we use, but the installation was straightforward. There is enough documentation for its installation.

We did it on our own. I only have one admin guy for its deployment. 

We are a regional research and education institute. We're using the free license provided for educational institutes.

I would recommend this solution. I would rate Jira an eight out of ten.