Jira Reviews

My primary use case is using the boards in working stories for freeing up the backlog and assigning tasks to my developer team. 

No other stats of graphics or reports from Jira are used. We use Grafana instead of that.

I really enjoy the easy way I can follow up the story's progress even when they are in progress or we test bug stories. When issues arise, they can play back to the team in order to fix all the bugs. They have a view of the backlogs in the current sprint and the next sprint. 

The initial setup is straightforward. 

There are many Jira add-ons available, however, we aren't using those yet.

The solution is stable.

We've found the scalability to be good.

I alternate Jira with Excel. I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira.

I've been using Jira for about four years. It's been a while. 

The stability is quite good. There are only some updates that are made by IT, however, it's working fine for me. I haven't dealt with bugs or glitches. it doesn't crash or freeze. 

The solution is scalable. I've tried other solutions, and this one seems to be the most adequate for my needs.

We have about 1,000 users worldwide. There are several projects running in several parts of the world. 

We do not plan to increase usage. We are using it as we need it and no more than that.

We've never faced any big issues and we have never had Jira go down. Therefore, we've never had a need to contact technical support. I can't speak to how helpful or responsive they are.

I found the initial setup to be pretty simple and straightforward. It was not an overly complex process. 

However, largely, we are just testing Jira. I can't speak to how long the deployment takes. 

I have three teams that can handle deployment tasks. There are six people in one, seven in another, and ten in the third one.

We do not use resellers or integrators to assist with the initial setup. We can handle the process ourselves.

I don't have any information in regards to the licensing or cost of the solution. It's not an aspect of Jira I handle. 

I have tried or tested other options such as Excel, Monday, Trello, Tetra. In comparison, for how I use it, Jira is the most adequate for my daily job.

We're a customer and an end-user.

Nowadays I'm using the web version of Jira for my client. I'm managing my boards, my sprints, and my backlog which are all working on Jira except the retrospectives. These are made in a code and not written down in Jira.

I would recommend the solution to others. It's easy to learn, easy to handle, and we've never experienced any downtime for a year and a half at least.

I would rate the solution at a nine out of ten. I haven't fully utilized the entire product, however, from what I have seen, it's exactly what we require. 

We are using Jira mostly for the workflow dashboards for our projects. For example, for now, we are using the Kanban boards at team levels and also between team cooperation levels.

The links between tickets are very valuable and the boards I found to be configurable and usable.  The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use.

I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues.

I have been using Jira for approximately four years.

Jira is easy to scale. We are implementing it for our team and for other teams, such as the relations teams. If you look at the different levels, such as the coordination levels, we are using it extensively on a daily basis.

In my team, we have less than 100 users using this solution but we also have other teams in our large company that could be using the solution. Our company has thousands of employees.

I have not contacted support.

The initial setup of Jira is straightforward.

We have a team in my organization that specifically handles the support of Jira.

The stability and performance are good, I have not had any complaints from people using Jira.

I would recommend Jira to others.

I have not used many tools to compare Jira with.

I rate Jira a seven out of ten.

We use it within our organization. 

It's to handle all the main technology projects. It's for managing mobile banking, internet banking, all the new products, and all technology-related projects.

We get the big picture of what is going on within a project.

The solution allows us to provide access also to the senior management, to see how things are progressing and to point out quickly what's going on, and help to focus energy on the things that are not going well.

The main benefit we got from the product is the consolidation. 

I like the roadmap or the new version with the roadmap that the solution offers. For us, the roadmap was a really great feature.

It's got very good portfolio management. 

The initial setup is easy.

The licensing is transparent. 

It's a stable solution.

Scaling the product wouldn't be difficult. 

Whether you are an expert in Agile or just it's the first time you are talking about it, it's a very user-friendly tool. It's a very simple tool. It's not complicated and even the integration and the usage is very simple. You don't need to be an expert. 

Whether you have small teams or big teams, it's the right tool.

We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product.

In general, however, as a solution, it's quite complete and I cannot speak to any missing features. 

I've been using the solution for one year now. 

At the moment, we have not had any issues with stability. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

At this time, we are not tackling scaling at the moment. The organization is not mature enough to scale up.

That said, based on the experience we have had now, if we want to scale up, it should not be that difficult.

We have approximately 200 people on the solution currently. Those users are mainly comprised of the software development teams plus some portfolio managers and program managers and the project managers as well.

We do plan to increase usage in the future. 

I have not had any interaction with them as we haven't had any major issues. We have a contract with the integrator, however. While everything is going well for the moment, we would have access to assistance if we needed it.

I've used Clarity, however, it was used in another organization.

The initial setup was not complex at all. It was very straightforward, very simple.

The full deployment took about three months.

We have four people capable of handling any management tasks related to Jira. 

We had the setup services handled by a reseller of Jira.

It was a very good experience. It was very fast compared to what we expected from the contract. It was a nice surprise.

We have yet to see an ROI as it's been just one year, including the three months of implementation. Maybe in the next six months, we can have visibility on that. For the moment, it's still in progress. We cannot say anything about any ROI.

We pay a yearly licensing fee for an enterprise-level license. 

It's quite similar to the pricing that they have on their website. It's quite transparent from their site. They have a package that charges per user, however, they have some scalable packages, for zero to 10 users, from 10 to 20, from 20 to 50, and so on. You can choose, depending on the size of your company or the number of users. The costs are quite transparent.

While everything is included in that package, the integration or the customization is a different fee. There's a project apart from the integrator, which may vary in cost.

We are just customers and end-users.

I'd rate the solution at a nine out of ten. There's always room for improvement, however, it's a very good solution.

I would recommend the solution to others.

My organization primarily uses Jira for project execution like managing the sprints, sprint planning, task creation and execution of the project on a sprint basis.

They also use Jira for other insights into how our team is performing and the velocity of the team. They look at the dashboard and report to see how are we delivering minimum viable products (MVPs) on time.

Jira offers tools for managing projects using Agile methodology. I think it is good to encourage the development team to use Jira, so that the organization benefits from the proper execution of projects on time. It helps our organization to execute in a better way.

I like the comment section. When you create a Jira task and work on it, sometimes product owners need to know the most recent status. I can go to the comments and then provide my updates stating how far I am. They can also refer to it and they can comment on it. It's for collaborating with other team members.

I also like using the filters in Jira. I can label all of the Jira tasks based on different business areas or whatever category I want. I can filter something that is related to what I've been working on. For example, if I am interested in APIs, I can filter all the Jira tasks with the API label and get all the API-related tasks, check the progress and where they stand. 

I can also get access to documentation such as the tester data and the other things that other developers have provided.

Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see. 

I have used Jira for the past three to four years.

In all the time I have used Jira, I have not had any stability issues. 

Jira is used by many of our teams and I have no concerns around scalability. 

There are around 1,000 users in my company who use it.

Jira offers Agile project methodology management and can be used for defect tracking and bug tracking. I would strongly recommend any organization wanting to use Jira, to work with the Jira team to understand what each product offers and how suitable it is for their organization. 

The Jira team could be consulted to understand the project, your department's requirements, and provide a proper way of managing the tool and advising what are the kind of roles you'll need.

I would rate it an eight out of ten.

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're using JIRA in combination with Xray as a test management tool.

The Xray module gives us test management capabilities, right. Where we can store tests and test executions and so on. That's basically where we moved our test out and we left Quality Center behind. 

With Jira, basically, you have a story. You try to estimate the story and then you have to try to have coverage for each story with test cases. We sometimes use it for our automation perspective. We're using the JIRA Xray API to write bad test results into the tool, through an API call rather than going through the UI. Our continuous testing pipeline in GitLab will automatically update the test results through the Xray API. That's it.

The thing that was helpful, in my opinion, was the reporting. I was able to do real-time reports myself without having to wait for data import. 

The product has lots of dashboards that could be created also in Confluence using Jira features. I really like that. I am able to make it transparent to everyone where we're standing in regards to, for example, test automation or test coverage. We could easily integrate Confluence with Jira, produce some handmade dashboards, or use the dashboarding inside Jira itself with the various reporting options there. 

It's totally sufficient to cover our use cases right now. I have no gap at the moment.

There is always a bit of a performance problem. It's a bit slow to load the whole data. When I load those dashboards onto Confluence, it always takes quite a bit of time to get all the data in Confluence. It's a lot of queries.

The only thing that was bothering me was the performance issues where it was very slow. 

We started using the solution three years ago. I've used the solution since 2016 personally. 

Stability has improved over time. It was crashing quite a bit and the minute it crashes, the organization kind of stands still. It's a huge dependence we have on it. However, it was 99% available in the end. Only some kind of maintenance announcements might affect it. Other than that, it was quite stable.

Likely every single user has Jira as we are fully delivering software with that. It's between three and 5,000 users. It's company-wide and there could be thousands of users. All the development work is documented there. It's used for our agile teams. You have teams that are using agile scrum.

It's very flexible and it supports both ways of working. It's very helpful also with child transformation. The whole organization moves into agile and everybody is relying on those dashboards and daily standups and it has heavy adoption. Everybody's using it.

The solution is easy to scale and that's a bit of a problem. It's highly customizable and you can also destroy Jira by over-customizing things. If you, for example, want to raise a bug and you have 50 mandatory fields, you kind of lose patience with it.

That's not really a Jira problem. That's the customization from inside the bank where there are lots of different requirements being put into the tool and it can destroy the user experience in the end if they over-design it. If it takes you ten minutes to raise a bug due to the mandatory fields. That's really annoying and that's a big problem.

Internally, I've used technical support. I have not had contact with Jira externally.

We have a separate team in the company who is dealing with all the support tickets.

There are three levels of support tickets and they probably have connections directly to Jira people or Xray people.

We're looking into transitioning into possible options in GitLab only. GitLab test management would be a topic. However, there we are not clear about the features yet.

We came from Quality Center, the fat client version, and we moved to JIRA Xray three years ago. Now we're making a decision as to whether we want to move away from JIRA Xray to something else. That's the open question right now.

I wasn't involved in the initial setup of the whole thing. I was just a consumer. We were just migrating our data over from QC into Jira Xray and that migration process was okay. 

We lost some data, however, in general, the assets were transferred over and we could continue there and leave the whole old world behind and start working on the new world. 

From a migration perspective, it was almost seamless. Afterward, you just had to learn a little bit. That said, it's quite straightforward. The JQL query language was something new at the beginning yet easy to pick up without big pieces of training. You can train yourself pretty well with the documentation that's available on the internet. I was able to teach myself almost everything without having to go into any training. 

I can't speak to the maintenance requirements involved. That's handled by another team entirely.

I don't have any details in relation to costs or licensing arrangements. 

We have an on-prem installation of Jira. I cannot tell you the version of it. I don't actually care, as long as I can store my stories. They're moving into a soft solution, potentially next year, with it.

I am very happy with the tool. I would recommend others to use Jira anytime, as it's super flexible and there's a lot of things that are not being leveraged at all. There's so much power in the product - we don't even know half of it, I would say, in the organization. 

I'd advise new users to not over-customize it. If you just get it out of the box, you already have a really good evolution and you tend to break it by over-customizing it.

I'd rate the solution at a nine out of ten.

We are primarily a software development company. We work on some very specialized software for the government. So, we use Jira as our primary bug/issue tracker. We are also looking to put some add-ins in it to help with configuration management.

We also use it for configuration management and task assignment, but that's all within the bug tracker itself. What's good for us is that we are not doing all of that in three different applications. That's very useful. I'm sure larger businesses can find other uses and plugins for it, but right at the moment, Jira is fulfilling our needs.

We think Jira is great, it's been a real help as an issue tracker for us. We have had no problems with it. It just works; it's always worked. We never lose any data. So, we're happy to try to keep it going in the future.

We are a small business and we're up to our ankles in getting code out the door on a regular basis. We do not have a lot of time for investigating new things, but Jira has saved us a great deal of time. It has a nice user interface and we can do a lot of things with it.

They are not supporting in-house servers anymore and I think I've got until January to port this to something else. The issue is not that it is difficult to move Jira to another server, but we have a relatively large database on an SQL Server that Jira either uses or created and we do not want to lose that data. 

We are not a very large company so that is a problem. A lot of our business is on Azure and I would prefer to have an Azure solution for our software management. At the moment, I'm trying to figure out how to move Jira over to Azure on our servers. As a small company, we just don't have a lot of time to solve those kinds of problems. So we may end up moving to something else if it turns out to be more difficult than we can handle. 

Everybody has to make business decisions and obviously, right now, we're not in that sweet spot for them. But, moving onto the cloud has its advantages too. 

We are using Jira regularly now and have been for about a year. 

My impressions of Jira's stability are good. We are running the Jira application on a Windows Server 2019. We also have a large SQL database server running on Windows that Jira accesses. So, there's a Jira database running on the SQL Server and the Jira app and it's never gone down.

Jira is a scalable solution. We have not run into any issues with it. 

We have used a number of things from spreadsheets to in-house-built issue trackers. But Jira worked right out of the box.

For a small business, this quality of a product for the price is really nice. I think we're paying $78 a month or something like that right now.

I would definitely recommend it. Now I'm a 10-person development company with about 30 staff members. If you don't have a lot of IT support and you're doing everything yourself, Jira is a great product for you. It's not hard to install and it just works.

We are using Jira for ticket management.

The solution has helped my companies efficiency with managing tickets throughout the life cycle.

We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface.

The solution could improve the Agile reports. They do have quite a bit of reports already, but additional reports would be a benefit.

I have used Jira within the past 12 months.

Jira is stable.

I have found Jira to be scalable.

We have a few hundreds using Jira in my organization. They consist of developers, project managers, and testers.

Whether we increase usage of the solution depends on what each team wants to do. There is some level of common solution approach, but I don't know for sure whether this is the direction that everybody is wanting to adopt.

We had to reach out to their support a few times. The support was good, I did not have any issues with them.

The initial setup was not difficult.

We have an IT team that supports the solution.

My advice to others wanting to implement this solution is to utilize the SaaS solution unless it is required not to. Having your own instance running in your data center or private cloud requires your own staff and resources to maintain and upkeep. It can be quite time-consuming work. Unless you are invested in something like that, there is a benefit of just using a SaaS solution.

I rate Jira a seven out of ten.

My primary use case of Jira is as our project management tool for monitoring and planning.

The most valuable features are the speed and especially the search capability - I don't think any other platform can compete on those.

The main area for improvement is the high cost of the product.

I've been working with Jira for two years.

There are some small issues with stability, like unexpected updates, but overall it's good.

I think you can scale Jira as far or as big as you want, it's very scalable.

Jira's technical support is easy to communicate with, and they are very responsive.

This product's cost is much higher compared to other platforms, but it's worth the extra cost. Some add-ons are only available at additional cost.

Jira is easier to configure than other platforms like DevOps. It's fairly easy to learn so long as you dedicate some time to it and is easier to use than other solutions. I would rate this solution as nine out of ten.

We are using it to organize most of our software development processes. 

Being a cloud solution, we usually have the latest version, but sometimes, we get a pop-up saying that there are some changes in a menu or some new features are there.

It covers most of the development process, and almost everyone uses it. We are using it for every role involved in the project, such as business owners, product owners, testers, developers, and DevOps. For example, the product owner defines a new feature, and then we take the feature and create stories and development, testing, or DevOps tasks. We then implement the new feature or changes to an existing feature. All the test cases and other things are in Jira. So, everything is done in Jira.

It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days.

Its search and reporting can be improved. They are already nice, but they can be further improved.

I have been using this solution for more than 10 years.

Its availability is great.

We have different offices, and overall, there might be about 2,000 people. There are no issues with its performance or service. Almost all roles in our company are using this solution.

Other people have experience with Jira's technical support, and they are quite happy with their support. Personally, I never had a case where I needed any kind of support.

It is a cloud solution. It just requires licensing. Of course, some support would be required for all users of Jira, which could be in thousands. It might not be an easy task, but overall, I don't think a lot of time is spent on its maintenance and support. It is a very trustworthy service.

It is certainly a long-term solution for our company and for previous companies that I have worked for. They have these long-term term licenses, but I'm not sure if they really pay on a yearly basis. They are certainly using it for a really long period and for a lot of users.

I would definitely recommend this solution. It is very popular, and a lot of my colleagues have used it before. It doesn't require a lot of learning time. It is very good to use. I'm quite happy with the service. Of course, it can improve, but personally, I'm very happy with it.

I would definitely give it a good rating. I would rate it a nine out of 10.