Jira Reviews

I believe we are using the latest on-premises version. 

Confluence, not Jira, is the most convenient feature with Atlassian. We use the product for knowledge management, the use of creating or documenting knowledge into a knowledge base.

I would like to have a future-proof idea of the cost and the roadmap for my class. This is in light of the fact that they are switching things up, promoting the cloud service and mixing different support levels.

The CMDB and knowledge platforms that are in the background of the ticketing tool should also be addressed. 

I have been using Jira for five years. 

When it comes to the question of stability, this depends wholly on the amount of resources provided to the virtual servers, since we make on-premises use. 

We have internal Atlassian experts, so it is tough for me to comment on the technical support.

The price of the solution could be lower.

We are currently in the initial stages of contemplating a switch from Jira. 

My advice is to work closely with Atlassian to make sure that all the designs are future-proof.

It is tough for me to Rate the solution. There are features needing improvement, but also many good things about Atlassian. As such, I rate Jira as a seven out of ten.

On-premises

We are using it for service management, change management, project management, and tracking the changes.

It is user-friendly, and you can manage your project according to the methodology you want. It is also easy to configure.

The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough.

So far, I've only used the project management parts. We are examining resource planning and sample plugins for the product. From my point of view, resource planning is a little bit hard to link with project management. Sample plugins are another part of the system, and we need to link it with project management in the BigPicture screen, which is a little bit hard. It would be valuable for us if we can do resource planning in BigPicture as well. Currently, it is another plugin, and you can only plan based on the people and not projects, and you cannot link it, as far as I know.

My company has been using it since the beginning of this year. It has been around six months. I have been using it for three weeks.

It is stable, and everyone generally looks satisfied.

We are trying to settle the project management part and widen it to all countries in our company. There will be many users.

We are working with a consulting company. Technically, we are okay because all of us are using it now, and there is no problem. We just need to see more details of some of the modules of Jira.

For its implementation and deployment, they have been working for one year.

Jira is a big platform, and you can use staff management, project management, and other fields that all companies want to use. If you use Jira, you will see the whole IT governance in one system.

With this solution, we can see the full picture in detail, but it can be improved. Resource planning is not easy for our project base.

I would rate Jira a seven out of 10. It will be an eight in the future. I need more time to work on Jira.

We use Jira product in the organization to automate the software development life cycle.

It's a very flexible product.

We can change the workflows as much as we need and we've done that already. 

The workflows are very easy to handle as far as scalability goes.

If there is a feature or a workflow feature, that is required and it's not available out of the box from Jira, from Atlassian, we have the marketplace buy from. There are a number of add-ons that we use. We have maybe 20 to 25 that fill in any gaps in the system itself.

The user interface is very detailed right now. It could be simplified if they consider targeting the user experience. Right now, on the screen pre-design, the amount of information on the screen is very high. The distribution is good, however, the presentation itself looks very technical. They should work to streamline the UI to make it better for users to digest the information.

I've been dealing with the solution for two years now.

The solution is very stable. We haven't had issues with bugs or glitches. It doesn't crash or freeze on us. It's quite good.

The solution is scalable in terms of the number of users and the number of features. The features we are using are mostly out of the box, however, we have added product management features and code delivered with the integration features. We also have added test management tools or add-ons to it including reporting and dashboarding as well. You can really grow it out and add as many plug-in apps and features as you want.

Currently, we have 500 users that interact with Jira within our organization.

We have good internal technical support for Jira in the organization and we use the Atlassian technical support only when needed. Thus far, we are quite satisfied with the level of support we receive.

I cannot give too much information about the installation, as we're similar to a consultant, and I don't want to get into too many details. As the installation engine, we took two days straight to deploy it and that is with the implementation.

For deployment, you don't need a huge team. We did it with two technical personnel. They are consultant level system administrators.

We're just a customer. We don't have a business relationship with Jira.

We're using the latest version minus one, due to the fact that it was installed year. That upgrade was last year and it is my understanding that there is another version coming up.

I'd recommend this solution to other companies.

The product is very scalable and it's very flexible to match any organization, however, the trick to using Jira effectively is that there should be a business process documented in place before using it straight. The mistake that many people do is they consider the tool as the base and they configure their processes according to this. If they work the other way around and have a great process between all cycles, and then implement that process on Jira, it's very beneficial.

Overall, I would rate the solution eight out of ten.

On-premises

The solution's most valuable aspect is its workflow sensibility.

The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways.

A lot of the user interface could be updated.

Technical support is lackluster. It could be improved.

They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.

I've been using Jira for ten years. It's been a decade now since I first started working on the system.

The solution is extremely stable. There aren't bugs and glitches. It doesn't crash or freeze. It's quite reliable.

The solution is absolutely scalable. If an organization needs to scale up, they can do so easily.

Technical support is pretty bad. They rely on partner companies for support and don't really have any of their own internal teams that can help.

The initial setup is not straightforward. It's quite complex. However, you do tend to get used to the process after a while.

The solution is quite expensive. I'm not sure of the exact pricing, however, I know it's not cheap.

We're an Atlassian partner.

I'm actually using various versions of the solution. I stick with versions seven and eight, mostly.

I'd rate the solution seven out of ten.

<ul> <li>Customizable workflows</li> <li>Agile / Scrum compatibility and offerings</li> <li>Granular access/security settings</li> <li>Large selection of add-ons</li> <li>Ease of use </li> </ul>

Since our service is customized to each client, the ability to customize workflow for each project's specific needs has improved productivity simply by streamlining our efforts.

We switched to JIRA this past February. So 7 months.

There is a steep learning curve for administration. While the tool is fairly easy for our users to understand and use, what it takes to set up the system to MAKE it easy for end users is fairly complex. There is a large amount of information to know and many interdependent layers.

We did not encounter any stability problems due to the JIRA itself. The problems we ran into were server-based and improved significantly after upgrading our server.

Not yet. =)

Customer Service: I would give it high marks. From an account service standpoint, all of my questions and requests have been replied to quickly and thoroughly.Technical Support: Medium-high. It mostly takes the form of Q&A within their Atlassian Answers forum that then leads to links of posted documentation on their Confluence pages. So there is a wealth of information and people able to offer advice and help. But it has a very "self-help" feel when trying to track down answers.

We did previously use a competing solution. We decided to switch based on several factors: cost, (lack of) support from the previous tool, and mostly we felt the strengths and weaknesses of the prior tool did not match up well with our needs and processes.

It was complex, but in a good way. We used a vendor called Service Rocket to help us through the process and they were magnificent. We spent several weeks with them as they got to know our process and needs to help tailor the setup solution. So it was complex in that we spent a lot of time closely examining our processes and workflows to make sure the solution fit accurately.

We looked at numerous other products. Some were more well-traveled offerings like Rally, AtTask, Clarizen, and Basecamp. Others were newer to the game like 10,000ft.

The most frustrating part of implementing a new management system is "you don't know what you don't know", so it's easy to miss which questions to ask or requests to make. JIRA has a LOT of knobs and levers to pull and is many layers deep in it's setup. If you're not intimately familiar with its offerings, I highly suggest using a consultant or vendor to help step through the implementation. I also suggest being specific in needs and wants. We’ve found JIRA is flexible enough to adapt to our needs more often than we have to adapt to its offerings.

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.

Private Cloud

We use Jira for enterprise planning.

We like team collaboration and cross-functional collaboration.

The history with Jira is that it is a bit complex for many users.

There are too many features.

The user interface is complex.

I have been working with Jira for five years.

We are migrating to the latest version.

Jira is pretty stable.

It is scalable enough.

We have 1,000 users in our organization who are using Jira.

We plan to increase our usage.

Before Jira, we did not use any other solutions.

The initial setup is straightforward, nothing out of the norm.

We had a perpetual license but have changed to a subscription.

We are not satisfied with the pricing. It has become more expensive.

We would prefer it to be cheaper.

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

I would rate Jira an eight out of ten.

On-premises

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. 

Public Cloud