Jira Reviews

It is mostly used for communication, managing requirements, managing defects, and managing stories. We don't communicate much through Outlook. The majority of the work-related issues are assigned to us, or we assign them to developers through this solution. I've been using this solution for managing requirements and defects. I have also been using it for logging user stories and general communication.

Best in ensuring 100% test coverage through forward and reverse traceability matrices capability that allows users to track User stories, SRS, Test Cases, Test Instances & Defects all using simple links. 

The most valuable feature is the feature of assigning. Whenever I have an issue, Jira doesn't stop at just letting me describe the issue. I can also assign the issue to a developer, and the developer gets notified about it. After he is able to work on it, he can update the status and revert back to me through the same platform. It really avoids a lot of communication over email and phone. This the feature that I really like about Jira. I always use Jira with my team.

Produce improvements suggestions:

User Interface/ User experience could be improved by expanding on visual capabilities of links such as  Stories, Requirements, Scenarios, Cases, & Defects.

User Dashboards could be improved by increasing ease of use of charts and other interactive options such as Boards.

I have been using this solution since 2011.

It has been stable. I haven't had any downtime or issues with stability. It has been working as expected.

In terms of integrating Jira with other apps, I've actually used Jira to connect to ADPART or other client defect tools. Sometimes, I had to use the connections, but it was not a problem. There is a standard procedure where I had to request for the details, and after I got the details, I needed support from the client to get it connected. There were no issues, and the process is quite standard. It is not fast, but it requires some time.

At my current company, only I am using this solution. We are a startup, and we have less than ten people working here. However, on my client's site, a lot of people are using it.

I've used their technical support only once or twice in my entire experience with this tool. Once, I was not able to log in, so I had to call them, and the other time, it was a problem with my virtual machine. It was not a problem with the tool. I was having problems getting in. I raised tickets, and then I had to call them. It was nice, but it took a little bit of time. Overall, the customer experience was all right.

Before this, I used an HP tool. I started with using Quality Center, and then I upgraded to ALM, and ever since, it has been Jira. Jira is open source, and some of my clients prefer open source, and they have been using it for a long time. Before Jira, ALM/Quality Center was my major go-to tool.

It was straightforward. I just got the details from the client, and I started using it.

Save by reducing errors and improving accuracy.

Start with requirement. If requirement requires tight security and confidentiality, it is highly recommended to employ expert assistance. Whereas if the requirement is agile in nature and is at very initial stages, it is best to start leveraging open source to some extent.

It was solely based on requirement and preference of business stakeholders.

Some areas of business require to run licensed and proprietary software applications whereas some can have the opportunity to leverage open or closed source software. 

It is essential to track efforts right from the beginning of the project i.e the from the day of planning and incubation to delivery and deployment. 

Our primary use case for this solution is development ticket status tracking. We use it for managing different kinds of projects. This is an online tool, where teams from anywhere in the world can use it.

This product has improved our ROI. Without this tool, our projects cannot be completed fully. Dependency cases among the teams cannot be resolved.

The most valuable feature for us is the capability of assigning a task to a developer and resolving it. This tool can be used anywhere and on any device.

The user interface and views on different devices should be improved. The customization feature can also be improved.

In terms of stability, there are very few failures.

Our impression of the scalability for this solution is that it's good.

We did not use a different solution prior to this one.

The initial setup for this solution is straightforward.

We used a vendor team for implementation.

Good. The return of investment is something that we have found to be very valuable.

We feel that the product is a good value for the cost. 

We did not evaluate other products before choosing this solution.

It is an excellent tool for project management.

Having a Technical Account Manager gives us someone who I can email about any of my questions or concerns about products, roadmaps, configuration and scalability options, etc. If I have an idea for something I want to do he might say "that’s a terrible idea", or "you might want to try it this way instead", because he has a depth of internal knowledge and context which most end users are unable to attain. This internal advocacy, contacts, and ease of communication are each tremendously helpful.

Collaboration on open action items and active ongoing projects. I spoke with my TAM about this issue and he completely agrees. There is no one system on which TAMs and their customers can collaborate on action items, ongoing projects, meeting notes, etc.

Began using Technical Account Management (TAM) in Nov 2014.

Yes. We were having an issue where we have to take one of their products offline to do a backup every night. I was certain there was a better way that it could be done, but on Atlassian Answers, other users were giving vague, hand-wavy responses. Our TAM was able to give us a couple different options, each of which will be able to save a department of 300 roughly 4 hours a night.

No.

We are just in the process of dealing with future scalability issues and having the TAM in place now puts us in a good place to address those concerns.

Very high.

Well above average. Their response time is good, and we are able to escalate what we need to escalate.

Yes, we have used several throughout the growth of our part of our organization. Most recently we moved off of Rational Team Concert from IBM. There is not enough time to tell you why I hate that product! It is one of the worst products I have ever used for ALM. It is not set up to encourage self-directed teams, despite its name. It says it can do whatever it wants, but it is not designed as a product to make people happy, just to make IBM's consulting organizations more money. Atlassian products are the exact opposite. A new team can be brought on and be working efficiently within minutes – with Team Concert could be hours or even days, if ever, before a team can be working well together.

The initial setup was very straightforward. The only complexities had to do with our own infrastructure. With Atlassian, either you can run the programs open to the world or behind the firewall. The default state for our systems is locked down, but Atlassian works best when their tools are able to connect to one another. This isn't a problem with the products, just an issue with our own infrastructure. I run local development versions of the tools on my laptop with no issues.

Completely in-house.

We did not look at any other complete suites of tools. We evaluated Rally Enterprise and VersionOne for project/defect tracking. Both of those options had decent levels of integration with our CI tools. Ultimately the value that the Atlassian suite gave us as a total package of discrete, but connected, components was above and beyond the piecemeal approach we would have had to take otherwise.

As an Enterprise customer, evaluate what you really need. If it's tech support above/beyond what comes with the subscription, go with the Enterprise tech support instead.

TAM is when you really need/want an advocate within Atlassian. For instance, our program and product management groups set up an on-site meeting with our TAM to discuss JIRA Portfolio, and they were able to ask questions of the Portfolio product manager as well as the TAM after a solid demo. Without a TAM in place, this type of thing would have been impossible short of sending everyone to the Atlassian Summit (User Conference) every year. That’s invaluable.

Another recent example is that we had a problem with a plug-in owned by Atlassian, but because we have our TAM in place he was able to get us in touch with the plugin developer directly and we've skipped weeks of struggle.

It's all about advocacy, insight into product roadmaps, best practices, etc.

We use Jira to manage what is happening in our projects, such as application development lifecycles.

The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution.

I have used Jira within the past 12 months.

Jira is a reliable solution.

I have found Jira to be scalable.

The price of Jira could be lower.

I rate Jira an eight out of ten.

We have really noticed an improvement in the way we work.

It's a really good product. I feel it really changed the way we work and at this time we're not looking to move to another platform.

The features on offer are great. It has everything we need.

The solution needs more integrations with Azure DevOps OnPrem.

I can't speak to any missing features. It has what we need overall. 

Company-wide we started using Jira this year, however, I've been using it since last year. The company hasn't used it for that long.

We aren't looking for another solution at this time. We're happy with Jira. 

As far as I know, we are just a customer. We don't have a partnership or anything with Jira.

I'd rate the solution at an eight out of ten. 

I work for an insurance company that has developers who need to be tracked. We're working on converting the spreadsheet into a Kanban flow environment. I'm the program manager/master. 

The solution is very powerful, has many good features, in particular a good reporting capability. I like many of the features, and I have the benefit of having a very skilled Jira administrator helping me out because I'm a PM. 

The solution is not as intuitive as it should be and you have to play around with the environment quite a bit before you get a handle on how things work. One of the issues is that it's usual for a ticket to have a primary developer on it and other people supporting, but that's not possible in Jira. They have a very thick policy and a ticket can only have one assigning, although it may be possible to do it as a number coding, I'm not sure. I'd like to see the solution include a feature whereby you can link stories visually, to explicitly show the connection between a user story and a task. 

I've been using Jira for several years. 

Scalability of the solution seems fine.

Technical support could be improved. When you submit a ticket, it can take two or three rounds before you get what you're looking for. I send the ticket and receive an irrelevant response, which doesn't help. You can go backwards and forwards with them and never get there which is very frustrating. I'm not sure if the user community is that helpful. I've submitted two questions but haven't yet received a response. 

The initial setup was quite complex. 

The solution is fairly good at doing a lot of things, and is potentially very good, but it takes some getting up to speed on. I've used a product called Kanban Flow, and that's very intuitive, very easy to use. Jira seems to be more complicated and requires having specialists on board so that if you have a problem, you can get help immediately without having to go through the ordeal of submitting a ticket and waiting two or three days to get a response, which may not be helpful at all. 

I rate this solution a five out of 10. 

We have a development team and we use Jira to manage our projects. We use several products by Atlassian whenever we create and work on a new project.

We have scrum masters who write new project stories, which are tracked by Jira.

The most valuable feature is project management.

The integration and management features need to be improved.

When you first start to use the interface, it is confusing.

We have been using Jira for about one year.

In my company, we have a lot of knowledge and experience with Atlassian products. We have not needed to contact technical support.

I have also used ALM Synchronizer and I find that it is better because it is easier to manage and it is a more agile tool.

My advice for anybody who is implementing Jira is to install the plugin from Micro Focus because it is a better way to manage the interrelationship between these two tools.

Overall, my experience with Jira is pretty good.

I would rate this solution a nine out of ten.

We use this solution for Agile Scrum-Based DevOps on AWS with a Linux, Cloud-Based SaaS environment for mission-critical applications.

JIRA has increased the transparency of DevOps and it has enforced systematic, process-driven, communication.

The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications.

This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number. I would like to see a more customized workflow, as well as support for the Google Doc storage of Documents.