Jira Reviews

The integrations with other solutions, such as BitBucket for pull requests and the check traceability, are pretty good. That's about it. I'm not a big fan of the solution overall.

The initial setup was pretty straightforward.

The solution, in general, is a poorly designed and confusing product. The user experience is not ideal and the user interface is convoluted. The interface in particular could use a big refresh as the actual navigation within the interface is not particularly smooth.

The work items structure is not hierarchical and that needs to be changed. It's too flat.

There's excessive scope for customizing the project and the platform. Therefore, there are too many integrations, which leads to very high levels of complexity in terms of management.

Key indicators that are useful to Agile teams such as burn-down charts or burn-up charts, cumulative flow control, et cetera, are available, however, they're not easily accessible from the default user view, whereas they should always be present. Key indicators must always be present. They actually take a couple of clicks to actually get to them.

I've been using the solution for two years. It hasn't been too long.

The solution is very stable. It doesn't crash or freeze. There are no bugs or glitches. It's reliable in that sense.

The solution is scalable. If a company wants to expand it, it can do so.

We have about 200 people who use the solution currently. They're mostly software developers but they're end-users as well.

While the solution is being used extensively, we're fine with maintaining our current level of usage.

Technical support is very good. We're satisfied with the level of support that is provided to us. They are knowledgeable and responsive.

I've personally used lots of other solutions, however, when I moved to this company, they already had Jira deployed. Jira is the only system of its type that's been used here.

The initial setup is not very complex. It was pretty straightforward. If a company wants to implement it, the setup should be pretty simple.

There's ongoing integration work on a project like this. Therefore, the initial setup was only a few days, however, then, as you add things to it, you add more time to the deployment.

We are a customer and end-user of the product.

I would highly recommend not using this product if your focus is software development. Organizations should seriously consider alternatives such as Azure DevOps or TFS, which are more focused on modern interfaces and more accurately modeled to modern workflows.

I'd rate the solution at about a three out of ten. It doesn't really offer a whole lot that's actually usable from a software development context beyond extremely simple and free alternatives.

We use this solution for project management.

It can be used across a team. Managers can assign tasks and then they can track the progress. They can put the start dates, end dates, and everyday comments.

They can upload the relevant files to that module.

Jira is used to manage a sprint, which is the terminology used in the agile practice of project management. Sprints can be tracked fully using the Jira software. A sprint is typically a part or a subset of the entire work. It has a definite goal.

For example, if I am building test software, and building the login page is one module, then I can track the work created from the starting stage to the end.

It's a part of an entire software application. If a login page of a website is a subset of an entire website, I can track that right from when it started, how long it takes, what is pending, and how long the control test is.

Basically, you can clump it all together as if it is a team and you can measure the speed of the team. It enables the predictability of a project and helps determine when it can go live.

All of the tracking features are the most valuable because it allows me to see where we stand today and every day. 

At the end of the day, I look to see what is pending, what is as per my expectation or as per the speed, and what is not going.

I can put in my comments or give a direction, or tag any other person if they need any help if they are stuck.

The user interface could be much better, although it's good enough to do the job.

I don't see the mobile application for this particular application. I use it on PC. I tried to download the application, but there are some constraints to using it. It doesn't link properly, it doesn't detect my Jira board, even when I have entered the name. I don't know how to use that app. I download and tried, but there is confusion. There is no clarity on how I can map my desktop account with the mobile application. There is definitely room there to improve. 

There should be a way to integrate the mobile application or in some way, make it more clear because at first instance, I didn't understand how to use it.

We have used Jira over the last seven months.

It's a stable solution.

We have a team of eight members who are using Jira. They are divided into teams with each team using different boards. 

For example, one team is managers who are using it, whereas another is a team of developers using a different board that can be created and used for their purposes.

I have not been in a situation where I have needed technical support. Everything has gone well.

The installation is typically done by my IT team. I don't have exposure to that.

Prior to Jira, we were evaluating Microsoft tools, but I don't recall the name. Possibly Microsoft Task.

We were evaluating Microsoft products for the same purpose.

The decision is a collective team decision. It may have been that Jira is easier to implement across the company.

It is a well-crafted product. I don't have any concerns.

I would rate Jira an eight out of ten.

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