Jira Reviews

JIRA is an issue tracking application, it in global development projects. JIRA helps teams to track and accomplish the items that need to be The great feature about JIRA is you can store the activity happening around an asset in one placeJIRA is useful in project management. It can reduce the rework in enterprise projects. You can also use JIRA Core for Project management, Task management, Process management, HR, Marketing, Legal and Finance projects. JIRA Core can be as per business projects need.

JIRA is very efficient. It helps us to create benchmark times to solve each ticket's severity. Burn down charts show your effort against the estimated time.

Active sprints. It is like a Kanban Board drag and drop backlog to assign, to do, and finish the task.

When creating Epic, Story, and Task, there is no provision to set estimated time. The estimated time can only be set once the ticket is created.

No.

No.

Excellent.

We have In-house project management tool. The report generation, burn chart are not so good. We Started to use Jira to  between different projects across geographic location

Straightforward.

In House

Its very nominal  prices per the features available.

No

JIRA is very good. With another tool, like Confluence, HipChat, Trello, Bitbucket, Bamboo, and FishEye. It creates a robust project and product management process.

I am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

It improved with many exiting features to manage user stories, planning and retrospective meetings very productive.

The documentation is very good.

The solution is stable.

You can scale the solution easily.

It's comparable to Azure DevOps.

It's a very complete product overall.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews.

It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories.

In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

I'm new to the company. Although I've worked with Jira before, I've only been at this company for one week.

Atlassian solutions for me are very good solutions. They are very interesting and very productive. As a user, it is necessary to have a unique portal to make traceability between sub-tasks related to code or programming. You can create and screen or implement a function or a class, related for example to the code that you are pushing in the repository or commit in the repository. If I open the sub-task, I will see the code related to the sub-task. It's very similar like Azure DevOps. Azure DevOps, however, has this functionality for traceability. This functionality will be amazing that Jira would implement something similar.

I prefer to use Azure DevOps instead of Jira for stability or the frequency of use. In my case, for example, I feel that more users, more companies don't think Azure DevOps makes a good choice due to the fact that the cost is higher than Jira.

The scalability is very good if you're carrying a lot of projects here, and if the company needs to have a lot of people to PEA development centers in Mexico. Our technicians can easily test the tool and scale it in order to develop projects.

We do plan to increase usage. We're already training more users. We're increasing quickly so that our teams will be ready for upcoming projects.

We have manuals, technical support, and also technical specialists in the company. I haven't had the opportunity to use directly call the technical support from Atlassian, however, the technical documentation that I have reviewed is excellent. We're satisfied with the level of service we have access to.

We also use Azure DevOps. They are both very similar. The main difference is Azure offers traceability.

The solution is easy to implement. We have the cloud version of Jira in the company, and we don't worry about maintenance, it's automatic.

The cost of Jira is okay. It's better than Azure DevOps. We don't have any licensing fees that I know of.

While I'm new to the company, it's my understanding that it is a partner of Atlassian.

We use the latest version of the solution, as we use the cloud, which updates automatically.

Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira.

On a scale from one to ten, I'd rate Jira at a ten. It's a very good product.

Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

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.

We use JIRA for maintaining tasks and bugs. Overall, we love using JIRA because it performs very well with a lot of tasks and a lot of dashboards.

Having a tool to manage all your tasks and all your bugs is very useful for any company. We use it a lot to keep track, to see how our development is going and how automation is going.

We use a lot of dashboards and a lot of queries to search for specific bugs related to specific versions. Also, we can provide it to all of our users throughout the company.

The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components. It gives you a lot of flexibility between the teams.

I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.

We have had no problems with stability. We're doing maintenance upgrades, but it has working well all the time.

We're not dealing with the scalability because we're not IT, but I don't think there is a problem with scalability.

We used Bugzilla but its UI was not as user-friendly. The end-user experience was very basic because it's a free tool. It's important to us that QA be able to track the issues and, of course, for the developers to be able to track all the tasks. So we're looking for the balance between performance of the user interface and the UI for the other workers in the company.

I would rate it at nine out of 10 because there is always room for improvement, but we love this tool and we use it a lot.

I would recommend JIRA. Compare all the tools for bug and task management. After that, you'll see that JIRA is by far the best.

Our primary use case for JIRA is for entering user stories into the login books.

The most valuable aspect of this solution is its ability to connect everything together. 

It also has good stability. 

I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. There shouldn't be the need to go through this. The process should be improved. 

It's not so good for testing.

I have been using JIRA for ten years. 

It has good stability until now. 

You can scale with it. 

We have around 35 users. 

I haven't needed their support. 

I previously worked with TFS.

There are a lot of similarities between the two. Especially in terms of working in the same field, tracking issues, and tracking bugs.

I would recommend JIRA to somebody considering it. I love working with it. 

I would rate it a seven out of ten. In the next release, they should make the process easier to be customized.

For QA, the most interesting for me are boards, backlog, and filters.

We finally started to use Git integration, so it is easy now to find a fix of a specific issue.

Filters: I never use a simple filter because it is not enough. When I have a complex filter and switch to simple, the switch is impossible. Also, even with complex filters, not all searches are possible.

Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches.

Make the product more user-friendly. It should be easy even for a person on his first day: to edit items, to select several items, to copy items. The product should be for people.

Two years.

Not yet.

Not yet.

Haven't used it.

Yes, I've used HPE Agile Manager. I switched because I switched the company I work for, and the new one works with JIRA.

I didn't install it, I only use the web interface.

Not my area of responsibility.

Not my area of responsibility.

1. "Start watching this issue" which sends updates to a user who has subscribed to this JIRA when there are changes made
2. It provides us with a view of historic changes that are recorded
3. It allows universal searches, even across multiple projects in JIRA, when we want to find the JIRA where a keyword was referenced

We use this as a primary tool to record all requirements and changes. This product is absolutely easy to use and does its job perfectly. 

My opinion of this product is that it is quite complete - from a QA standpoint.

I've used it for four years. We have this integrated with SpiraTest, so all incidents raised in SpiraTest are replicated over to JIRA and vice-versa.

JIRA was the solution we used throughout. It had no competition.

This is a good product, and I would back it every time.

We using this solution to handling all of our development and support tickets.

We have found the structure, functionality, and how Jira handles the tickets most valuable.

The performance could be improved in the future.

I have been using this solution for approximately four years.

We have had some issues with stability.

The scalability is good for what we are using it for. We have approximately 20 people using the solution in my organization and we plan to increase usage.

The technical support could be more responsive.

We have one technician handling the deployment of Jira in my organization.

There is a monthly license required for this solution and it is expensive.

I would recommend this solution to others.

I rate Jira an eight out of ten.