Jira Reviews

Overall, everything with it is great. I found it super useful, as it is customizable for different teams and users.

The following definitely need improvement:

• UI 
• Speed 
• Mobile app functionality.
  

It is consistently slow.

I use Jira for user stories, tasks, bugs, track releases, track backlogs issues, burndown, and test reports.

Jira has helped our company because it is easy to track releases and deployments. It is easy to track which tickets have been done or are still pending and left to be completed.

Jira's most valuable features are ease of use, simple to understand, and highly flexible. Additionally, you can use kanban or scrum which is a benefit.

The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes.

The out-of-the-box version of Jira has minimal to no testing functionality. I have to use Zephyr to be able to track testing. The time logging is also not easy to use, or user-friendly.

In the next release of Jira, there should be test cases in the test reports. Better burndown and burnup reports should be enhanced. Additionally, the usability of time logging could be better.

I have been using Jira for seven years.

Jira is stable and reliable, we have not had an issue.

I have found Jira scalable.

We have approximately 50 people using the solution in my organization.

I use the solution extensively in my organization, I use it daily.

I have not contacted support from Jira.

When I came to this company I had already used Jira. Previously, I was using quality control from Quality Center and Azure DevOps.

The initial setup was straightforward overall. The process takes only 10 to 15 minutes. However, the setup could improve.

We did the implementation of the solution in-house.

We have two administrators that do the patching and maintenance of the solution.

I would recommend Jira to others.

I would advise others to be sure to do the reports correctly because there can be some challenges in reporting and in the testing phase.

I rate Jira an eight out of ten.

We use Jira for software development and issue tracking, enhancement requests, and software lifecycle management.

Jira has benefited the organization because it's necessary for doing our job well. We would need to have Jira or a similar tool. For example, it's could be similar to working with documents, you need Word or a similar tool.

The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations.

Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability.

It depends on your usage pattern because if it's more configurable, you can configure it to be a very different kind of tool which is a benefit.

I have been using Jira for approximately 10 years.

The performance is not very good for Jira but the reliability is good.

Jira can handle a lot of tasks. In my project, we have approximately 50,000 issues to be resolved and it worked well. However, the overall solution is slow.

We have approximately 25 employees using Jira in my organization of a total of 2,000 employees.

I use Jira moderately while other of my colleagues use it daily.

I have not used the support from Jira.

I have been using Allegra previously.

I was not around for the initial setup. However, I tried to configure it later and it is not easy. It is not as easy as it should be.

The solution is on the cloud, there is minimal maintenance.

The price of Jira is reasonable.

My advice to others thinking about implementing Jira is if you only want it for the standard flows and use it as an issue tracker in a software development setting, it is a good solution. We are using the online version. If you are in need of changing workflows or appearance, fields, screens, et cetera, Jira is not able to do this well or it's not possible at all.

Jira has found its place in our organization and it does those tasks. They should focus on speed and stability, and in that order. It's excellent with regards to preexisting integrations but it is poor at configurability.

Whether Jira is a good solution for you depends on your use case. From what I have seen creating different workflows in Jira is not good.

I rate Jira a five out of five.

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 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.