Jira Reviews

We use it to trace our business needs development.

We have some nice dashboards out there where we can track needs for clients or track internal projects.

This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page.

With the time differences that we all have, it is very hard to kind of get on a call and centralize the information in person or during meetings. This solution makes it possible. 

One of the most valuable aspects of the solution is the fact that everything is traced on one ticket on Jira. We know exactly what has been done and what is left and we share the same feasibility we are assigned. We don't have to wait for team updates or emails or calls or even reminders. We just need to look at the same ticket and we know in real-time exactly what is happening. Without Jira, I don't see how we would be able to manage and trace in a very consistent, effective way.  At least, not across all of our development initiatives.

I have never been trained on Jira, to be honest. However, it's easy to navigate. Even for somebody who is never on it, it's very simple to pick up and understand. The only caveat is that when you get a bit more in detail, or you have some business requirements, you don't have documentation that you can just go and consult to enrich your portal or access.

One aspect of Jira that is very nice is that we are able to integrate other tools that our company is using. For example, we do use Salesforce for our support team and that's linked to Jira. Slack, as well, is also integrated into the system. It makes everything so much easier.

Jira has recently updated their UI, but more can be done to make it even better.

One thing that is missing is notifications that we can send out in an automated fashion so that we don't have to log into Jira every single time. We do have dashboards on our navigation pages, but we need to log in to see the current status. I can't just click reports every once in a while to trace or track projects, I have to log in to see. I'd prefer it if the data automatically came to me instead of having to go seek it out. 

It's possible the dashboards and the reports are something that can be properly configured on our end. However, I'm not the Jira administrator in our company. I probably just don't know how to do it. Jira may actually be able to trigger these kinds of reports. However, if they don't have this functionality, it should definitely be added.

 I have been using the solution for four years now.

We've never experienced any downtime with the app. I can't recall any bugs or glitches. There haven't been any crashes of any sort. It's very reliable.

I would say the solution is pretty scalable. Every single project team in our company uses it. Our staff, our BA, our developers. We do also have DevOps teams using it. Everyone uses it for different purposes. Our company, over the past ten years, grew exponentially. We've tripled our size and we never had any downtime with Jira. 

We have business owners, developers, quality testers, business analysts etc. on Jira. We have internal consultants from professional services teams, who trace the needs as well so that they can transmit information to their clients. All the top management personnel go to Jira to consult the dashboards as well. If they wish to trace the progress that their teams are making, they can do so. The solution is basically used in every aspect of the company, and as the company grows, so does the usage.

I've never had to reach out to technical support, so I can't speak to how they are.

When I joined the company, we already had Jira. 

I wouldn't consider it complex at all.

I wasn't here at the initial setup of Jira, however, in our company, we have a Jira administrator. Whenever we have a project to review and need to know how it's laid out and how we can place them better, etc, it goes through this person. She analyzes the needs and does it for us. 

 She knows the tool pretty extensively, but we don't rely on external consultants to do it. We have somebody from our company who does it for us and acts as our own Jira professional. They would be the one that basically helps you with the setup for your project needs.

I don't handle the finance side of our relationship with Jira.

As far as I know, no other solutions have been considered as we've been pretty satisfied with this tool. 

I'd advise other companies to go for it and try using it. Jira is one of the biggest players in the market. It's a scalable solution and very user-friendly. The onboarding is quite simple. I have never been trained and I've been using it for the four past years. Whenever there is a new release on Jira, we get a guide, which is helpful, and instructions as we use the latest version that comes in the form of pop-ups on your screen. If you want, you can just disregard it, but once you discover them, you can just hover over with your mouse and you can see the new features. If an organization is looking for something that will be easy for its workforce to adapt to, Jira would be a smart choice.

With the communication and the bridges that we've established with other tools, it's helping other teams get the information they need without having to get the Jira license or get them to go onto Jira. They just need to find their tool and they get the update from Jira in real-time.

We have various use cases for it, one being for object storage. It's a government entity so that's what they use. 

It has improved my organization because it gives us collaboration. 

The most valuable feature is that it is somewhat flexible. 

It's a pain getting it on the public, it costs too much.

It's also difficult to migrate through, things don't always tie-up. It's not easy to use and it's not as intuitive as it should be. I stay away from it as much as possible.

I have been using Jira on and off for ten years. 

I would say that it's stable.

I would rate it a five out of ten because it gets the job done. 

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.

I use this solution for general issue management, software planning, and change management.

This solution is a one-stop-shop for issues and plans.

Issue linking has enabled teams to trace issues.

I like the dashboards and Kanban boards.

The development links to GitHub are critical.

The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily.

We use JIRA for software development projects and the implementation of business workflows. Our company runs more than one hundred projects on a single instance server. Besides core IT projects, we have implemented business processes on dedicated JIRA instances to manage high volume (greater than five thousand issues per month) non-conformities for some business lines. 

Transparency of development projects, as well as approval processes for some business projects, has improved massively. Interaction of business units and IT happens very often via JIRA and considered to be very helpful. As many of our developments are requiring some level of compliance, the workflow and documentation of approvals are very handy. 

There is a very flexible configuration of "issues" and related life cycle. On top of it, the number of "add-ons" is overwhelming and of very good quality. I would consider the reporting capabilities to be the best feature, as ultimately the visibility of issues allows management of the projects.

My main concern is the administration of projects, especially user groups, and this requires root access rights but there is no concept of layered admin rights. Projects can be managed by a limited admin, but the creation of projects needs root admin rights. In decentralized project ownership, this gets tedious.

We used an open-source system called Mantis, which was considered unsuitable for use outside the IT world.

The setup of JIRA is straightforward.

To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money.

We went right away to JIRA without evaluating other options.

JIRA, its add-ons, and the Atlassian product world are already very powerful and it is difficult to name significant blank spaces.

This is a very powerful solution. Get some advice and training to make the most out of it. You may miss out on some of the capabilities if you don't.

We use this solution for product development and issue tracking.

This solution provides us with a centralized view of issues, simple time registration, and excellent integration to Bitbucket.

The most valuable feature of this solution is the source linking on the commit level to git.

The speed of this solution needs to be improved.

Backlog pruning and visualization are poor. 

Uupdate:

Speed has improved slightly in backlog view with Jira 8.0, but there is still room for speed improvements.

It's difficult to group and manage the backlog and priorities on multiple simultaneous epics to get clear overview of how the backlog reflects a planned roadmap. (perhaps due to the fact that we have too many issues in the backlog)

We use this solution for our scrum team and user story management.

This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on.

This solution is very easy to set-up and use. It is very intuitive.

The permissions can be challenging to get right.

We use this solution for Agile project management and BAU work delivery in sprints / DevOps.

This solution has helped with team collaboration and task delivery.

The most valuable feature is the Burndown Chart to see work that is outstanding.

The reporting needs to be improved.