Jira Reviews

1. Its agile support is fantastic! Whether you are an agile expert, or just starting for both scrum and kanban teams, the whole agile process is supported
2. Requirements log
3. Story board
4. Dashboards are a great feature to stay on top of what is going on in all the projects you are managing
5. It's accessible from practically anywhere, whether you're on a mobile device or desktop across many OSs and browsers

Integrating JIRA with HP Quality Center gave our dev team and management a new window to participate/track the defects Testing Team reports from. This integration is absolutely powerful and made defect sharing with different parties a peace of cake. Now we, the testing team, can report defects on our own "beloved" HP QC, and these defects gets sent automatically or upon request to different JIRA Projects and to different project parties and teams.

I would say test management, as it's a generic issue tracking tool, and not designed specifically for test management. So, the only support for test cases is the ability to mark them as passed or failed as part of the test execution, and that's the whole test, not step by step like Quality Center. It does have many test management add-ons that can be bought, and some of them can perform close functionality to what HP Sprinter does, like Bonfire, but it does not provide video recording. It doesn't provide version control for Test Cases, and integration with Test Automation and Performance Testing tools is cumbersome.

I hate the fact that I have to buy an add-on for each feature I need. Some people might see this as positive thing since you buy only what you need, but again, not all add-ons are provided by Atlassian, and hence support and quality is subject to different providers, which is again is cumbersome, and not many people would go on with.

Reporting also needs improvement, as I need to be able to create my own custom reports and be able to export them, and screen shots doesn't work all the time.

If you are an agile development team, go for it. I would advise that f your dev team have problems accessing HP Quality Center, go for it and integrate Jira with Quality Center.

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. 

Our company is a consulting company and then we are an Atlassian partner as well. Therefore we use many functions of Jira. It's sometimes project management and sometimes to communicate to outside customers.

The solution is very fast.

It's a very useful tool. Jira is very useful for project management for internal projects. 

We can easily communicate with many things easily in Jira.

There's the ability to easily customize the product. There's lots of great potential functionality.

The solution is stable.

You can scale the product very well.

We'd like to see more collaboration tools implemented within the product itself. 

The product needs to allow for more communication between individuals and teams. 

The solution could always use better reporting. 

I've been using the solution for four or five years. 

The solution is very stable. There are no bugs or glitches. it doesn't crash or freeze. 

This is the type of tool that would work well for any size of organization, from a smaller company to a very large enterprise. 

The product is very easy to scale and extend the user license. In terms of functional expansion, for projects, it's very easy to expand. You can do so in no time. It's very quick.

For the most part, we are satisfied with technical support. Sometimes in some areas, if you find a bug on Atlassian, they respond quickly. However, sometimes, they are slower. It can really vary. For the most part, they really try to get to things quickly. 

The initial setup is different and is case by case, however, for a single person or scrum team, it's not too hard. The process is simpler on smaller setups. The more processes the company needs, the more complicated the solution gets during implementation. 

We have our own engineer team internally that handles maintenance. We have no problem with maintenance tasks. It's not too hard to handle. 

We provide implementation services to our customers.

Jira pricing is very difficult to pin down. They stopped another licensing version earlier in the year, in February. Now they have only data center licenses and then cloud licenses. These are more expensive than a server license. With a server license, you pay once. When you get a cloud license, it's an ongoing annual cost. We would have preferred if the old licensing model was kept.

We are Atlassian partners. 

We are using the current version, the latest version right now.

We use both cloud or on-premises deployment models. It's a hybrid approach.

I'd rate the solution at a nine out of ten. I'd recommend the product to other users. 

We primarily use the solution for our own projects.

The solution, for the most part, offers good usability.

The ordinary user has an interface that is very clear.

It's very easy to collaborate, especially on-site when there are a lot of moving pieces. It's a great collaboration tool.

Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly.

For admin to get permissions and stuff like that for their members it's a little confusing sometimes. That said, the rest is very clear.

The integration of what we call "Issues" in Jira could be better. The Issues integration with Bitbucket Pipelines could be better. If Jira can provide an easier way to configure and use this functionality, that will be helpful for workers.

I've been using Jira for more than ten years now. It's been a while at this point. 

I looked at other options, however, Jira is so famous and well known that I did not have to look for other software.

We are a customer and an end-user. We use Jira for internal projects. I'm a Java architect.

I'd rate the solution at a ten out of ten. I'm very satisfied with its capabilities. 

We use this solution to manage our projects.

Jira is a great software. There is not much to complain about, other than it doesn't fit very well into our current Microsoft environment.

Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian.

The only thing in our current setup that is a bit difficult is that Jira is a bit of a black box. Only we see it, our customers do not. I know that we can change it but we have not done the work to do it.

Jira is not compatible with our current Microsoft infrastructure. 

We are using SharePoint along with WorkPoint in our environment, which is used for document management and process management. For projects, it is a better connection between HelpDesk and the projects. Moving into SharePoint would help.

If Jira would be interested in offering a SharePoint version, it would be beneficial.

I have been working with Jira for approximately five years.

Jira is a stable product.

We have approximately 50 users in our company who use Jira.

I am satisfied with the technical support of Jira. It's fine.

I have tested Plumsail Helpdesk. There's only one thing that worries me. Due to GDPR, we cannot use email yet in Plumsail. That is the only thing, use email to create tickets.

I don't know where the mailbox is in Plumsail, otherwise, it just ends up in us using SharePoint. It looks very promising.

It is very affordable at the entry-level. When you get larger, the pricing becomes very, very steep. It is the same for many other solutions, but I find it expensive when you get larger.

We are currently using Jira but want to move the help desk to SharePoint. 

We have a Microsoft environment. SharePoint HelpDesk would fit better into our environment. As we are larger than we originally started, we have to make some changes to our current setup.

I also find Plumsail HelpDesk quite interesting.

I don't know what to compare it to. It is not an A product, but it's a strong piece.

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.

I use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

I have been using Jira for almost one year.

I don't work too much with Jira. I use it only to see the reports, and I don't feel that there are many bugs. It is stable.

It is not too expensive. It is just comparative to other tools like Microsoft Teams.

I would recommend this solution. We are interested in migrating to Jira and using it as our internal tool for agile projects and for controlling the IT software development cycle for projects like consulting or API. It will be more used for agile projects. It is a good tool. We also have the latest version of Microsoft Teams, but it is limited. It is better to use Jira.

I would rate Jira a nine out of ten.

We primarily use the solution for product development efforts and documentation. We use Confluence as well for documentation.

Most of my work is keeping track of what's been going on and identifying what is blocking future work. What I like about this solution is you can create a consolidated customized dashboard out of your files to identify what's been going on and identify who has how much data assigned to them. You can begin to understand where roadblocks are and how to streamline efforts effectively. It's been helpful. 

The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything. While it should be a standard thing across the company to have labels created in certain way, the system should be able to pull up suggestions of labels that are close. 

The product could be more intuitive. 

If something isn't getting resolved, we generally aren't getting any alerts to warn us to this fact. We don't get any visibility on if something's been open for a few months even if it should have been closed after a few days. We need some sort of system that shows us items that are lagging.

I've been using the solution for about six months to a year or so. It hasn't been too long. Our company has been using it since they started doing development work.

In my experience, most of the time it's very stable. Sometimes we have a few bugs here and there in Jira. However, it doesn't affect our work in a very big way. It doesn't crash or freeze. It's reliable.

I'm not sure about the whole company, however, on my team, we use it extensively. We have around 30 to 35 people using it on this team. Obviously, they are using it on other teams as well, however, I don't know the count of each team.

In terms of scalability, we are able to add new users as needed, and that has never been a problem for us.

I've never had to reach out to technical support. I don't know how responsive or knowledgeable they are.

I didn't previously use another solution, Jira is the first product I've used for this purpose.

I actually was not involved in the initial process of the setup, therefore, I can't comment on the process. I have no idea as to if it was difficult or straightforward.

I'm not aware of any regular maintenance that is needed on the product.

I don't deal with the financial aspect of the product. I cannot comment on if it is overly expensive or not as I don't handle billing or payments.

We're just a customer. We don't have a business relationship with Jira.

I'm not sure of which version of the solution we are using.

I'd recommend others go ahead and try the trial version of the product. If, after that, it seems to fit your needs, a company should go ahead and implement it fully.

Overall, I would rate the solution nine out of ten.