Jira Reviews

When you are engaged in an Agile development environment, most of the handling and tracking of the stories are handled in Jira. It can also be used for handling and tracking requests in a ticketing system.

I am a consultant from the quality and design part of the work that we do, and I help people introduce tools into their system. Currently, I am only working with one customer that is using Jira. In the past, I have had five or six who were actively using it.

This solution covers almost all of the types of uses that we have, from an Agile perspective. All of our requirements are supported by it.

This product provides you a good view of the status of your projects.

When I was managing projects that started from epics and moved to multiple tasks, I found that the integration of epics and user stories could have been a little easier. I've seen people struggling to use that aspect of Jira. I think that there is some ease of use that could be brought in to improve certain things.

I have been working with Jira on and off for the past six to seven years.

This is a stable product.

I have not used Jira for really huge projects. I have had groups of between 30 and 40 people and for that size, there were no issues with scalability.

We have asked a couple of questions from technical support and I don't recall having any issues with that. Everything was as expected.

I have not completed an installation myself, but my understanding is that it is quite straightforward. I am familiar with cloud-based deployment but I believe that it can be deployed in a private environment, as well.

One of my customers told me that they were receiving better pricing for a similar tool from Microsoft. Specifically, the total cost of ownership was cheaper with Microsoft.

This is definitely a tool that I would recommend to people, depending on their needs.

In summary, it is a good product and the only room for improvement that I can see is that it needs better integration.

I would rate this solution an eight out of ten.

We have a service desk for customers. We have the whole flow from customer feedback throughout, committing with a relation in the code in Bitbucket.

We have the tracking and tracing, including all tracking of the issues all the way from the customer throughout the JIRA prioritization in backlogs and sprint planning and connecting those through the actual code commit in BItBucket. It's all done through JIRA to the service desk issue and back again to the customer. The entire ecosystem is quite connected.

The best features depend a bit on the project going on. We have some project managers for the Classic Project setup and all the features that come along with the Classic Projects. 

From my point of view, the NextGen Project in the cloud solution is really easy to start up with and it's quite flexible in how you put up columns and move issues and tickets throughout the status and columns that you put up. 

It's really flexible. From the Atlassian point of view, I can see they are moving towards more Next-Gen Project handling. The features from the Classical Projects are being continuously rolled out towards Next-Gen Projects. Of course, there's still lots of ground to cover.

It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it. There's some approval function or a step via the Atlassian team to be able to actually endorse your apps throughout their marketplace. However, it's very smart to have collaboration between the company and third parties. Whatever functionality is lacking, there's most likely an app for it. 

I've seen some updates and subscriptions where you can get newsfeeds if you subscribe. They are focused on making the solution as responsive as possible. For instance, they have enabled some features called Project Archiving. If you're done with some project work, you could choose to archive everything related to it. Therefore, it won't be upfront taking resources from your solution, however, you'd still have access to it in the future.

Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed. It's my understanding that the reason they started doing the Next-Gen and changing up the whole dual-end functionality is probably because of how heavy and big everything was getting. It had gotten pretty complex within the Classical Projects. 

It's quite time-consuming picking up the Classical Projects. They've gotten quite heavy and it's hard to use them in a productive way. There are just so many settings and possibilities. It's very complex and time-consuming, however, on the other hand, it's got everything you need in terms of functionality.

We've been using the solution for a year and a half now. It hasn't been too long so far.

The solution is quite stable. We haven't faced any stability issues.

The solution is quite scalable. They also allow you to archive old projects so that they don't take up space on your product, and that can help you scale. You might need a specific kind of subscription in order to archive, however.

I don't really have much experience with the technical support team at JIRA. I've been reading the community tickets mostly. Most of what I've been curious about, I've been able to find the answer myself via the community or the WIKI. 

You can communicate with other users, which is really smart. It allows you to discuss best practices effectively. At the same time, I would guess that some of the users there would be actual Atlassian employees that are commenting and guiding. Overall, the community space is quite helpful. Therefore, I haven't really had any issues or tickets or any need to connect with a technical team in Atlassian.

One of my colleagues actually had an issue when a new user was invited before he had opened his 365 email. He had not logged in to the email account. Therefore, when the invitation was sent from Atlassian or from JIRA, I can't remember exactly which module, but then there was feedback that this was not an active email account, which made Atlassian revoke the whole user. Then, when he actually logged into 365, he wasn't able to connect to JIRA due to the fact that the email had been marked as expired or not an active email. He sent the request to Atlassian and they opened up a ticket and everything was fine within a couple of hours. It was really quick. That I think is probably the only dialogue we've had with the technical support in Atlassian and it was pretty positive. I'd say overall we're quite satisfied with their level of support.

The initial setup's level of complexity varies. If you use the Next-Gen Project, you can get it up and running in, I would say, five minutes. That part's quite easy.

You can also just subscribe and you can get the free version. I really like that kind of subscription that you can start with quite a few features available. You can get it started for up to five to 10 users without any cost. Then, when you start getting the ball rolling or the projects rolling, you have to actually insert your credit cards to both get features unlocked, and also to add more people to the projects and to the solution. 

If you want to, you can add on quite a lot of features and connect with the apps from the Atlassian marketplace. That's also a really nice possibility. You can just click, add apps and it takes about 30 seconds. Then you have added functionality injected to your solution.

I would guess we are using the latest version of the solution as we're using the cloud solution. I'm guessing that it's continuously updated automatically.

I'd advise others to consider the solution. However, It depends on what they're trying to achieve. There are a lot of easier project management tools like Monday.com, for instance. It's a lot easier to get up and running.

If your vision is to become a larger software development company, monday.com might be something that is usable for project managers. However, it wouldn't be a good tool, at least how I've seen it, to connect everything together as we're able to do in the JIRA cloud with all the connecting apps. I would guess we would be able to integrate Monday to JIRA or something like that.

It's really easy to get JIRA connected to Confluence and Bitbucket and to have the service desk as well. That way, everything is in one place. Again, it depends, on based on where you're heading. If the company is looking for easy project management, there's a lot of tools that would be just as good as the JIRA. If you're looking to distributing the teams and connecting a whole ecosystem, then definitely JIRA is a good pick.

I'd rate the solution seven out of ten.

We use Jira to manage scrum projects for the different projects in our company. Our business is a development company that uses the cloud version of Jira to manage the sprint and releases for each project for each client. We manage scrum and cascade projects with our clients.

Jira allows us to manage the project in a visual way, where you can easily see your sprint board and you see the status of your project, as well. It helps us to finish the sprint on time and easily move issues that are not finished to the backlog or to the next sprint. 

The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project.

The boards also help us to determine our velocity, and if we reach the release date it helps to determine which issues need to be moved in the event they will not be finished on time.

We would like to see the integration of a lite-version of Confluence, just to manage some of the templates and documents.

Without a plugin, implement the Route in projects created before this feature did so in the most recent versions of Jira.

I've been used Jira since 2016, and it helps us a lot.

Requirements management.

It enabled us to track and manage product commitments over the entire enterprise.

One form for each feature/item.

Better ability to add numbers in ad hoc queries and search results, e.g., total development cost estimates.

We didn't use a different solution.

We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

It handles all of the issues that we need it to do.

It is very flexible, so we can do pretty much what we want with it. 

I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.

It is stable.

It scales up well.

We have a team who administrates technical support. They handle this interaction with JIRA. Sometimes it takes a while to get a solution, but they solve everything. 

Before, we used a homegrown solution. 

Almost everybody uses JIRA nowadays because it is the most cost-effective solution.

I was not involved in the initial setup. 

I do know the initial setup was pretty complicated. The user interface could be better organized and easier. 

It does not cost that much.

We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

It is very capable, but also very complicated.

Most important criteria when selecting a vendor: reliability.

User friendly, easy to set up and maintain. Great integration along other Atlassian tools. Application can be enhanced either with free plug-ins or you can create your own.

Seamlessly merged efforts between quality and R&D.

Missing a Requirement Management piece on the suite.

We use one version of Jira internally and we also have another version of Jira that we use externally for our customer. We've been using it for both.

Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product.

The Defect section could be improved. When you're trying to keep track of the requirements and the Defect section, this setup could be done better.

I was struggling to set it up. I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira.

We have been using Jira over the last 12 months or more.

On a scale of one to ten, I would give Jira a seven.

To be a ten, there should be more options where you just click and drag. That would be nice. It's hard to copy and paste requirements. You lose your formatting and everything. So just simple navigation stuff should be improved.

We use Jira primarily for Agile development and change management.

The most valuable feature is its flexibility. There is flexibility in the structure, lifecycle, and workflows that you want to work with.

The interface is user-friendly.

I would like to see more robust release management within the tool. We're not able to use it at this time because of compliance issues within our industry. At this point, I'm not confident that it can meet the requirements.

I have been using Jira for about two years.

This product has steadily improved since the time I started working with it.

I would rate this solution an eight out of ten.