Jira Reviews

We primarily use the solution for project management purposes.

The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening.

The prompt board really helped us out on projects. The scrum boards and the representation of the product backlog that helped us a lot as well. It's great for project management.

In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities.

There needs to be more training modules and more emphasis from the company on proper training and product overviews so that users really understand its capabilities and can actually use the solution effectively.

I've been using the solution for nine years.

I do recall that there were a few times when servers went down, however, I don't really remember that much about why it happened. Usually, it got fixed very quickly. Largely, the usability was good.

In our organization, we had about 200 people using it and we didn't really have any problem with scalability. 

Technical support is good, however, we haven't really used them on many occasions. We never have really dug into the solution to understand it, and therefore we didn't really need the help of technical support to walk us through anything.

We're just customers. We don't have any type of professional relationship with Jira. We aren't integrators or resellers.

I'd rate the solution seven out of ten. I'd rate it higher, however, if the solution wasn't quite so dense and complex. It would be helpful if there were training modules to help teams and users better utilize the full solution. As of right now, we've never really mastered the solution to its full capacity. I'm sure the solution has much more to offer, however, we have only really dug into some basic features. Our organization doesn't really emphasize the usage of the system.

I'd recommend those considering using the solution to really get some training before they begin and to maybe try doing some pilot projects to test its capabilities. Jira, as is my understanding, does offer a free trial, and new users would benefit from taking advantage of that.

On-premises

• Agile, scrum project/sprint planning
• Bug tracking
• Workflows which help track the current state of tasks.

• The organisation is more flexible and agile.
• Tasks are easier to track. 
• Generally faster and more focused.

• Sprint planning
• Overviews over tasks and which assignees are doing what
• Specific workflows for projects.

• Add relation for workload estimation between stories and subtasks
• Linking to Confluence could be implemented. At the moment links can only be created from Confluence to JIRA, not the other way round.

One to three years.

It possesses excellent customization and serves the basic requirements: multi-project, products, customers and multi-level of users.

• We now have an excellent helpdesk ticketing system with follow-up and escalation.

• We used to have add-ons for remote support but it's not working, and it does not have powerful CMDB to help in building our KB and self-service for our clients.

Ticket management: We have our custom-defined ticketing number for each customer/product which helps in identifying the issue from the ticket number.

• It should be able to open a channel with a customer through chat or remote desktop.

• It should be able to define my KB articles and link it with a self-service ticket.

More than five years.

We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

It handles all of the issues that we need it to do.

It is very flexible, so we can do pretty much what we want with it. 

I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.

It is stable.

It scales up well.

We have a team who administrates technical support. They handle this interaction with JIRA. Sometimes it takes a while to get a solution, but they solve everything. 

Before, we used a homegrown solution. 

Almost everybody uses JIRA nowadays because it is the most cost-effective solution.

I was not involved in the initial setup. 

I do know the initial setup was pretty complicated. The user interface could be better organized and easier. 

It does not cost that much.

We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

It is very capable, but also very complicated.

Most important criteria when selecting a vendor: reliability.

JIRA comes with a workflow designer which allows to design and keep track of execution of pretty much any process (similar to what a BPM solution would do but cheaper). In the new or existing workflows you can define new "statuses" which you can use as "Queues" to handle your process status or requests.

In principle, JIRA was designed to follow software development projects, but we are also using it as a solution for our call centers to follow on "Learning Administration System" processes.

It allows you to extend and define any new entities (record types), define sub-tasks, links between records as well as define new fields, screens and customize your UI based on your needs.

It also integrates very well with other applications thanks to its Restful API. In my case I integrated with JIRA from Webmethods EAI middleware as well as from SQL Server 2014 SSIS.

JIRA has a marketplace where many plug-ins are available (some for free) to extend any missing features, as well as it comes with an SDK to create your own one if needed. In fact, this is one of the biggest potentials from my point of view.

Among others Atlassian (JIRA's company) has two powerful plug-ins

• Service Desk (to control SLAs in top of your processes) - actually not a plug-in a product on top of JIRA.
• JIRA Agile which allows to follow Soft Dev Projects using SCRUM or KANBAN methodology.

• We deployed JIRA and JIRA Agile plug-in to keep track of our software development cycles using SCRUM methodology.
• It has been our product of choice for some time now in order to deploy Learning Administration Systems for our customers.

I strongly believe that ease of use for the administration part (workflows, screens, field definitions) could be improved. Sometimes it is difficult to understand "where you are" when administering JIRA.

As a Test Analyst my first requirement is to have a tool where I can create a repository for all my test activities like test cases, test execution, defects and reports. Zephyr is an add-on which provides facility to use JIRA as a test management tool. We can write test cases, add versions, create test cycles and execute cases. To make life easy JIRA comes with a dashboard where I can add different gadgets to generate reports on different criteria.

My organization uses Wiki and JIRA both for requirement gathering, but very few know the capability of JIRA as a test management solution. People in the past used to write and execute test cases in WIKI and also log the defects from there. This not only made it difficult to manage the test cases and defect, but also there are no reports which can be extracted out of it. It becomes very difficult to fetch efficiency in each test cycles. Also, we were not able to track test coverage because we couldn't link requirement with test cases in Wiki. But after JIRA provided us a feature to use it as test management we are managing all these very effectively.

Though JIRA can be used as a Test Management tool, it is not complete by itself. There are still a few niggles in it as compared to other products like HP ALM. We can export the reports in xls or pdf. Also whenever we fail any test steps, the test does not fail by itself, we need to manually select fail from status drop down. JIRA does not provide any lock feature for a test case if any person is working on that case. In fact, both people can assess the same case at the same time.

I've been using JIRA for the past 2 years.

I found JIRA to be a stable product and didn't have any issues with the response time as compared with HP ALM. Only a couple of times during last 2 years it was down for few hours.

I worked on HP QC 9 & 10 before JIRA. There were no issues with these tools to switch to JIRA, but the tool used fora project always depends on management, user benefits and cost involved in it.

• Great user interface - it is light and very user friendly
• Web technologies - no need to install any local ("thick") clients on PC, just web browser
• JIRA is very customizable and has a modular structure - this is very important, when an organization has often changing workflows
• Powerful reporting and filtering systems
• Time tracking and workloging
• Fully customizable desktops

I advised my friend to introduce JIRA at his organization and I helped him with this. Here are some results after about two months:

• Employees stopped to write on colourful stickers and leave its at their monitors
• My friend and his manager can see what each employee is doing and find lazies
• Each project participant began to think before writing (earlier someone could say something but after some days his/he worlds were forgotten, or he/she might say that he/she didn't say that, etc);
• Employees started to plan their time and try to work faster and better
• Customers of the organization now can create tickets and requests via JIRA, no phone calls, no email conversations. The result - most of requests from customers are processed faster.
• A customer can see the time tracking of his tickets, so he can plan future requests and calculate current and future payments (and all that without phone calls).

There are some little bugs and features which need to be resolved, but they're not so critical. I think JIRA should have features like drafts of issues as Confluence has drafts of pages.

I've used Atlassian products for about 8 years.

Earlier versions of JIRA were more difficult to deploy, but current versions are deployed very easily. I have good knowledge of Linux, and I have never experienced difficulties with JIRA installations, even the early versions.

No

No

I used many other solutions before but my manager chose JIRA. I started using JIRA about 8 years ago and the choice was made by my manager as well. Now when I start my own project, the first thing I do is starting to configure JIRA to the project's requirements and after that I can start my project.

It was straightforward.

My first setup was just for 10 users with a license of $10.

I used many other solutions, but the most popular I used was RedMine, Lotus Notes, TaskFreak, and Bugzilla.

The main thing you should think about before you start implementing JIRA is ask yourself - "What result do I want to get from the solution? What problems do I have? What problems do my employees have? You should dream about your ideal team of employees and you must make your dreams a reality, and JIRA will help you with it".

I'm quite happy with it. 

The solution works well and does what it needs to do. It has been reliable.

The pricing of the product is fine.

We've never had an issue with technical support. We're happy with them.

I don't really have any areas for improvement. It works very well for what it is. I don't have any suggestions.

We'd like to see Jira have more integration with a development ID.

I've used Jira for six years at this point. It's been a while now. I don't use it as much as I used to, however, I still use it.

The solution works well for us. We don't have any issues with performance or reliability. There are no bugs or glitches. it doesn't crash or freeze. 

Technical support has been fine. We are satisfied with their level of attention and have been happy with them overall. 

We currently use Azure Boards, which is kind of a competitor to Jira, and one of the main reasons why is that it's more integrated with the development life cycle.

The pricing so far has been okay. I don't have much to comment on.

We're just a customer and an end-user.

I'd rate it as an eight out of ten. 

On-premises