Jira Reviews

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

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.

JIRA gives you all the features you need for organizing your work within one team and across teams in a very efficient and structured way. It is more than just a ticketing system and more than just a project management tool.

It is very user-friendly and very structured which makes it very easy to ask people from non-technical departments to come and join you within JIRA projects.

The amount of plugins is astounding, and many of them have a surprisingly high quality. While some are free, some other plugins are very expensive, but at the same time worth the money (at least this is what I think).

JIRA could be basically used to organize the work of a whole company, which is why it is so valuable.

JIRA helped us to work across teams and sites, while staying efficient and reducing communication overhead to a minimum. Since it plays very well with other Atlassian products, you can make sure that other members of the staff find JIRA issue related information much faster than in the traditional way (e.g. asking, search engine etc.).

JIRA is written in JAVA and therefore a bit hard to trouble-shoot. It also is very expensive once you have a lot of users. And since it is very flexible, it can also lead to situations where you loose overview of permissions, custom issue types etc. It also takes too long to create your own custom fields and issue types since you have to work yourself trough many layers of abstraction and features. But this is a well-known downside of flexibility and openness.

I have been using JIRA for more than 2,5 years.

No, deployment and upgrading was always straightforward.

Sometimes, it seems that JIRA gets a little slow. But is is very hard to say if the network connection, the underlying system or JIRA itself is the one to blame.

Not yet.

I used a heavily modified version of Sugar CRM, which was basically a custom solution. Never again.

The initial setup was very easy.

Since JIRA gets really expensive when having a lot of users (and maybe plugins), you should try to avoid letting everyone in by default. Maybe it is better to only give those users access who really could benefit from this product.

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.

1. Its agile support is fantastic! Whether you are an agile expert, or just starting for both scrum and kanban teams, the whole agile process is supported
2. Requirements log
3. Story board
4. Dashboards are a great feature to stay on top of what is going on in all the projects you are managing
5. It's accessible from practically anywhere, whether you're on a mobile device or desktop across many OSs and browsers

Integrating JIRA with HP Quality Center gave our dev team and management a new window to participate/track the defects Testing Team reports from. This integration is absolutely powerful and made defect sharing with different parties a peace of cake. Now we, the testing team, can report defects on our own "beloved" HP QC, and these defects gets sent automatically or upon request to different JIRA Projects and to different project parties and teams.

I would say test management, as it's a generic issue tracking tool, and not designed specifically for test management. So, the only support for test cases is the ability to mark them as passed or failed as part of the test execution, and that's the whole test, not step by step like Quality Center. It does have many test management add-ons that can be bought, and some of them can perform close functionality to what HP Sprinter does, like Bonfire, but it does not provide video recording. It doesn't provide version control for Test Cases, and integration with Test Automation and Performance Testing tools is cumbersome.

I hate the fact that I have to buy an add-on for each feature I need. Some people might see this as positive thing since you buy only what you need, but again, not all add-ons are provided by Atlassian, and hence support and quality is subject to different providers, which is again is cumbersome, and not many people would go on with.

Reporting also needs improvement, as I need to be able to create my own custom reports and be able to export them, and screen shots doesn't work all the time.

If you are an agile development team, go for it. I would advise that f your dev team have problems accessing HP Quality Center, go for it and integrate Jira with Quality Center.

My primary use case of Jira is as our project management tool for monitoring and planning.

The most valuable features are the speed and especially the search capability - I don't think any other platform can compete on those.

The main area for improvement is the high cost of the product.

I've been working with Jira for two years.

There are some small issues with stability, like unexpected updates, but overall it's good.

I think you can scale Jira as far or as big as you want, it's very scalable.

Jira's technical support is easy to communicate with, and they are very responsive.

This product's cost is much higher compared to other platforms, but it's worth the extra cost. Some add-ons are only available at additional cost.

Jira is easier to configure than other platforms like DevOps. It's fairly easy to learn so long as you dedicate some time to it and is easier to use than other solutions. I would rate this solution as nine out of ten.

Our company is a consulting company and then we are an Atlassian partner as well. Therefore we use many functions of Jira. It's sometimes project management and sometimes to communicate to outside customers.

The solution is very fast.

It's a very useful tool. Jira is very useful for project management for internal projects. 

We can easily communicate with many things easily in Jira.

There's the ability to easily customize the product. There's lots of great potential functionality.

The solution is stable.

You can scale the product very well.

We'd like to see more collaboration tools implemented within the product itself. 

The product needs to allow for more communication between individuals and teams. 

The solution could always use better reporting. 

I've been using the solution for four or five years. 

The solution is very stable. There are no bugs or glitches. it doesn't crash or freeze. 

This is the type of tool that would work well for any size of organization, from a smaller company to a very large enterprise. 

The product is very easy to scale and extend the user license. In terms of functional expansion, for projects, it's very easy to expand. You can do so in no time. It's very quick.

For the most part, we are satisfied with technical support. Sometimes in some areas, if you find a bug on Atlassian, they respond quickly. However, sometimes, they are slower. It can really vary. For the most part, they really try to get to things quickly. 

The initial setup is different and is case by case, however, for a single person or scrum team, it's not too hard. The process is simpler on smaller setups. The more processes the company needs, the more complicated the solution gets during implementation. 

We have our own engineer team internally that handles maintenance. We have no problem with maintenance tasks. It's not too hard to handle. 

We provide implementation services to our customers.

Jira pricing is very difficult to pin down. They stopped another licensing version earlier in the year, in February. Now they have only data center licenses and then cloud licenses. These are more expensive than a server license. With a server license, you pay once. When you get a cloud license, it's an ongoing annual cost. We would have preferred if the old licensing model was kept.

We are Atlassian partners. 

We are using the current version, the latest version right now.

We use both cloud or on-premises deployment models. It's a hybrid approach.

I'd rate the solution at a nine out of ten. I'd recommend the product to other users. 

We use Jira for project management for the development teams. Additionally, we do backtracking and managing the backlog but it is more of a development team tool.

There are a lot of plugins in Jira and we purchase the ones we need.

Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too.

I have used Jira for approximately 10 years.

We have never had an issue with the stability of the solution.

We have approximately 400 people using the solution in my organization.

The support from Jira is good.

The configuration can be complicated, there are a lot of options.

We have a technical team that does the implementation and maintenance of the solutuon.

The basic price of Jira is reasonable, but for each plugin, we have to keep paying more. When you add it all up, it can be expensive. The main problem we face is we are forced to purchases plugin licenses for users who are not going to use them. For example, we have Jira licenses for approximately 450 people but if we only want a purchase a plugin for few people it is mandatory to buy the license for the 450 people who have Jira licensees. This is a problem because sometimes we need plugins for the product manager or for people in charge of the report, not everyone. For us, it can be very expensive in the end, they should alter this policy to allow plugins for only a set number of licenses.

My advice to those wanting to implement Jira is to have a lot of support. In our company, we started out small with only approximately 25 people and then we expanded quickly. Jira can be complex to manage, and it is better to have some advice or some people to help with the implementation.

I rate Jira an eight out of ten.