Jira Reviews

We primarily use the solution for customer service and managed services, and for all the workflows for the services. It's also a bit of a CRM. We use it largely for technical support.

The solution provides an integrated platform for customer service. It's good at organizing our technical support for clients.

The solution has been very stable overall. We haven't had any issues with performance.

The pricing is reasonable. It's not too expensive.

The UX and UI could be better. It's something they need to improve upon. It needs to be updated and made more modern.

It would be ideal if the solution could be available as a mobile application.

We would like the solution to be a little less costly, although, overall, the price isn't bad.

I've been using the solution for five years or so. We've been using it for a while at this point.

I've found the stability to be very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance has been good.

We've never reached out to technical support for help in the past. I wouldn't be able to speak to the level of service they provide.

We did not previously use another solution. We do not want to switch to something new at this time either.

Unfortunately, I was not a part of the company when it was originally set up. I have no idea how the implementation went. I wouldn't be able to comment on if it was easy or difficult and/or how long it took to deploy.

While, of course, in general, we always want the pricing to be lower, it's pretty reasonable. The costs aren't too bad.

We are just a JIRA customer and an end-user.

We are using the latest version of the solution. I'm not exactly sure of the version number.

We do not plan to switch to another solution. We're quite happy with this product overall.

I would rate the solution at an eight out of ten.

Our primary use case for Jira is for requests for tracking the software development.

We use Jira for the process, especially for password tracking. We're the issue management team for development. We are quite new, so I was very interested in ITSM documentation provided by Jira. But, I needed time to readjust that to our organization as per the line of business.

Overall I think it's helpful, but I need some time to absorb all the knowledge.

People have different opinions about whether it has improved our organization. I think it is quite a valuable tool and platform to streamline tasks, make project plans, and manage the release events.

The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence. The documentation is another supporting part for development. I didn't go that deep, so that's what I see as the end user.

In general, it's very convenient for people that work in the software development business.

In terms of what could be improved, it is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira.

So I hope those will be considered soon. I think for some, the help documentation has been hard to track, so that I had a bit of difficulty finding the solutions. I'm the end user. I'm not the problem solver.

I have been using Jira for less than a year.

It does have some bugs or glitches sometimes. Like with Confluence, it always has some glitches, like the last edits I made minutes ago. It happens sometimes.

I don't know about the scalability. I just use the very basic one. 

Only our IT people are using it. It's easier for IT people to understand it than anyone else.

We have our technical support from our vendor. They are very supportive.

No, we didn't use another solution previously. We used to manage those processes manually, like the spreadsheet. That's why we would like to switch to the Atlassian platform for some automations and for a mature platform to help us.

We had our vendor help to set up originally. Later, we made some customizations by other means. But because this is still at a very early age for us, it's a bit random on previous customizations. There were some blockages for people to understand from different perspectives. But I think so far the business people may not understand those procedures because it was originally designed for the coders and for the software development business.

We are using the Community license for Jira since we are a not-for-profit organization.

I think the technical support and the customization of the line of business are the most important points for me as a BA. I don't think the license for a business is low. 

We think - so far so good. 

On a scale of one to ten, I would give Jira an eight out of 10.

Nothing is perfect.

We mainly use Jira software, including Jira Issue Manager, for bug tracking and project management, and have done so for over a decade. Then in the last six years we have also used Jira Agile in a lot of our project management work. We use the enterprise version of Jira.

There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training.

The simplicity of Jira is the part that I like the most, as well as the way in which it can be extended. For example, I like that you can send data to and from Jira easily, and it integrates well with lots of third-party plugins.

In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful.

When I first started using Jira and we were in the middle of coming up with a solution, I found that there could be better separation of tasks when it comes to user stories and epics. For example, right now we can take users and sub-task them, but the developer is not able to easily ask for or request a task as a separate thing to work on.

Other than that, I would definitely appreciate more kinds of features in general. But we have already requested these from Jira ourselves with their voting system. These requests are in their backlog now and we hope to see them in future soon.

We have been using Jira for more than ten years.

I feel it is quite stable, not least because it has been around for a long time. For the last few years, we have never see any issues from our location or any other location that our people use it from.

We have never had to use Jira's support as far as I know. 

I wasn't fully involved in the initial enterprise setup of Jira, but I remember first trying out some of the plugins on my laptop and I found it all rather easy. And for the people in charge of the main setup, they were able to install it and set it up quite fast.

We are using the enterprise license which is nice because it ensures that we always have the latest versions of Jira software. 

I would definitely recommend Jira for project management and similar uses, as well as other products from Atlassian like Bamboo.

Jira isn't what you would call a "coded solution" for scrum or anything like that, but it's able to do a lot of different things for people who are looking for that kind of thing. If you are looking for a custom-made solution specifically for agile or scrum, then you can go try other products like Valley or others. But if you want a good general-purpose project management system with solid integration solutions like Bamboo, then I think Jira is the product for you.

I would rate Jira an eight out of ten.

We are using the solution for project and defect management, and task tracking.

There could be some improvements in the project management and portfolio level features. I think they could bring more flavours of Agile to Jira, that would help.

I have been using the solution for approximately eight years.

We have found it to be very stable.

The solution is very scalable and flexible. It's one of the best products that we have been using. We currently have 80 users using the solution.

The configurations for the installation are very well documented on Jira sites. You can just go there and it has everything you need. The installation did not take much time, it was straight forward. 

We had one internal administrator do the implementation, the configurations are straightforward.

I would recommend this product to others. 

I rate Jire a nine out of ten.

We primarily use the solution for bug tracking. It's for customer support purposes.

The solution is quite easy to use. It's very user-friendly. The product is very easy to understand.

The solution offers very good tools for Agile teams.

The pricing of the product is very good. It's not too expensive.

We're more focused on other solutions. Jira could be more, for example, like Micro Focus, which is what I mostly work with currently.

I've been using the solution for about seven months at this point.

I'm not sure if the product is stable or not. I don't have any insights into that aspect of the product.

I don't know if the solution is scalable or not. It's not an aspect of the solution I'm responsible for.

I'm not sure how many users are on the solution currently. I'm not sure if there is a plan to increase usage just yet. That might be a question for our company in the next year or so.

We tend to handle technical support internally for the most part. I can't really speak to the actual technical support from Jira as I haven't dealt with them for the most part.

We are also using Micro Focus.

I'm more on the customer support side of the product. I didn't really handle the setup process. Other members of my team handled the implementation.

We've found the pricing to be quite good. It's not overly expensive. It's very reasonable and affordable for companies to implement.

We're just customers and end-users. We don't have a specific business relationship with Jira.

I'm not sure of which version of the solution we're using currently. It's my understanding that it is the latest version. I'm not sure if we are using the cloud or the on-premises deployment version.

Currently, I'm more focused on the Micro Focus product as opposed to Jira. That's more where my expertise is at the moment.

That said, it's pretty easy to use and I would recommend Jira to other organizations for that reason.

Overall, I would rate it at a seven out of ten.

We are using Jira for tracking and management.

It's an open-sourced product that is easy to customize.

Stability is an area of concern and it needs improvement, otherwise, it's a good product.

In the next release, it should be more stable and have more APIs to integrate more plugins with it.

The first time that I used Jira was in 2011. 

I am using the older version that was released in 2019.

It's not a stable solution.

The number of users is in the hundreds.

We will not likely continue using this product. Our customers are evaluating other solutions that are more stable and scalable.

We have not contacted technical support.

Previously, we did not use another product.

The initial setup is straightforward. 

The migration took a week to complete.

Depending on the use cases, I would either recommend Jira or not.

I would rate this solution a six out of ten.

Right now, I'm just trying the solution out. I'm doing a POC.

The solution helps a lot with scrums.

It's great for development. 

The documentation is quite good.

It has some automated software testing which is useful.

I'd like some more features around software testing. I'd like to see some more stuff done around data testing. That's what I'm most interested in.

They could be better around generating documentation and essentially helping with test scenarios, test cases, or test results in a way that is more user-friendly.

The product needs to be more flexible to adapt more effectively. Sometimes you fix the style or the format and it might not suit the environment. I'd like to be able to more effectively configure it.

I've only used the solution for less than a year at this point. It hasn't been too long.

The solution is quite stable. It's not really buggy and it doesn't crash or freeze. It's pretty reliable.

The product can scale if a company needs it to. They should be able to expand it to have it meet their needs.

I haven't really dealt with technical support. I study the solution mostly on my own. I've never spoken to them and therefore can't speak to how their services are.

In a few months, once I have used it on a deeper level, I may get the chance to reach out. However, as of right now, that has not been the case.

The initial setup is not complex at all. It's quite straightforward. We didn't have any issues with it.

I'm not sure how long the deployment takes. I'm a lecturer and consultant, and therefore my role is more to help people use the tool rather than set up the tool for them.

I use the free version of the solution. We don't pay for it at all. 

I use the current version of the solution.

Right now, I'm on the free version. I'm just trying it out right now, to see if I like it.

I would recommend the solution to other organizations.

Overall, I would rate it at a seven out of ten.

It is mostly used for communication, managing requirements, managing defects, and managing stories. We don't communicate much through Outlook. The majority of the work-related issues are assigned to us, or we assign them to developers through this solution. I've been using this solution for managing requirements and defects. I have also been using it for logging user stories and general communication.

Best in ensuring 100% test coverage through forward and reverse traceability matrices capability that allows users to track User stories, SRS, Test Cases, Test Instances & Defects all using simple links. 

The most valuable feature is the feature of assigning. Whenever I have an issue, Jira doesn't stop at just letting me describe the issue. I can also assign the issue to a developer, and the developer gets notified about it. After he is able to work on it, he can update the status and revert back to me through the same platform. It really avoids a lot of communication over email and phone. This the feature that I really like about Jira. I always use Jira with my team.

Produce improvements suggestions:

User Interface/ User experience could be improved by expanding on visual capabilities of links such as  Stories, Requirements, Scenarios, Cases, & Defects.

User Dashboards could be improved by increasing ease of use of charts and other interactive options such as Boards.

I have been using this solution since 2011.

It has been stable. I haven't had any downtime or issues with stability. It has been working as expected.

In terms of integrating Jira with other apps, I've actually used Jira to connect to ADPART or other client defect tools. Sometimes, I had to use the connections, but it was not a problem. There is a standard procedure where I had to request for the details, and after I got the details, I needed support from the client to get it connected. There were no issues, and the process is quite standard. It is not fast, but it requires some time.

At my current company, only I am using this solution. We are a startup, and we have less than ten people working here. However, on my client's site, a lot of people are using it.

I've used their technical support only once or twice in my entire experience with this tool. Once, I was not able to log in, so I had to call them, and the other time, it was a problem with my virtual machine. It was not a problem with the tool. I was having problems getting in. I raised tickets, and then I had to call them. It was nice, but it took a little bit of time. Overall, the customer experience was all right.

Before this, I used an HP tool. I started with using Quality Center, and then I upgraded to ALM, and ever since, it has been Jira. Jira is open source, and some of my clients prefer open source, and they have been using it for a long time. Before Jira, ALM/Quality Center was my major go-to tool.

It was straightforward. I just got the details from the client, and I started using it.

Save by reducing errors and improving accuracy.

Start with requirement. If requirement requires tight security and confidentiality, it is highly recommended to employ expert assistance. Whereas if the requirement is agile in nature and is at very initial stages, it is best to start leveraging open source to some extent.

It was solely based on requirement and preference of business stakeholders.

Some areas of business require to run licensed and proprietary software applications whereas some can have the opportunity to leverage open or closed source software. 

It is essential to track efforts right from the beginning of the project i.e the from the day of planning and incubation to delivery and deployment.