Jira Reviews

We are using Jira to manage our development sprints.

The most valuable feature is working with sprints and having the ability to create sprints. You can create and move onto the next one.

Also, for example, while I don't use a lot of plugins, when you have a ticket then all of the information you can put into it is centralized.

There are so many opportunities that you can create almost anything.

The sprint-related graphics need to be improved.

They are using story points for the sprint breakdown graphics. When you have five large stories with several story points, in the first week of the sprint, nothing gets done. This means that you have a flat line and then, in the end, all of the stories are done at the same time. So, we created all of the graphics but they were useless because it was just a horizontal line and then at the end of the sprint it dropped down to zero points. Basically, it was a square.

In the next release, I would like to see a good graph that takes into count what you put into your stories.

I have worked with Jira, on and off for four or five years. I last used it in April, a few months ago. I have always been working with the latest versions.

It's a stable solution.

Jira is scalable, but you will need knowledge of every team because in every organization you have several teams that work differently.

You need to understand and know how to scale and be prepared.

It doesn't require many people to maintain Jira. 

You can configure a lot yourself, depending on how many rights you get in the application.

If you have enough rights, you will have a lot of opportunities to configure it in the way you like.

I would recommend this solution to others who are interested in using Jira because you can do a lot with it. However, I think that as you start working, you should start small. Work with it and try to configure things that you really need. 

Involve the whole team in what you are going to use and how you're going to use it.

I would rate Jira an eight out of ten.

We use this solution for Agile project management and BAU work delivery in sprints / DevOps.

This solution has helped with team collaboration and task delivery.

The most valuable feature is the Burndown Chart to see work that is outstanding.

The reporting needs to be improved.

Eighteen months.

Our primary use case for this solution is work management and task management.

We use this product quite extensively, and we're planning to roll out a module for the Accounts Department to be able to map manpower costs to project work, directly. That is something that we're working on right now.

Based on the flexibility that it offers us, we can adapt to different projects with different cycles. Based on whatever cycle we are working on for a particular project, we can configure the solution to suit us. This helps us to manage the work, essentially in one place, and we have visibility of all projects that are going on in the company.

The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs.

The plugin management needs a lot of work. Sometimes you have issues with plugins and it stumps the vendors, as well as the Atlassian support.

I think that more extensive reporting would be very good because sometimes it is a hassle for us.

Approximately ten years.

It is pretty stable. I would give it a ninety-five.

In terms of stability, it is pretty impressive and I would give it ninety-five. We have not had any load issues.

We currently have between twenty-five and thirty users, whose roles range from Software Developer to Chief Executive Officer.

I would rate the solution's technical support an eight out of ten. 

I have used a couple of solutions, but I have used this one for my entire career in working with different teams. I have had to integrate my own solution as well, but the majority of my work has been using this product.

I have worked with both the hosted application and the cloud version. For the cloud, the initial setup is very easy. You can do it in basically two minutes and you're out but for the server, the setup entails a lot more.

This is quite understandable because you're going to be managing it by yourself, onsite. For the Cloud, it's pretty straightforward, but if it's the server version then you need a lot more focus and experience to be able to configure it correctly.

The last time I installed a server instance we had to do it overnight and it took me between four and six hours.

The deployment was done in-house.

There is no maintenance required for the cloud version.

I would say that we have seen ROI with this solution. When we are looking for some sort of information, it just makes our lives much easier because we are able to do things without having to talk to anybody. You know exactly what is going on. It limits personal interaction but helps us to get our jobs done quickly.

Licensing is on a monthly basis, and it is based on what you use. There is a base cost and then as you include other items, the cost rises. Our last payment was perhaps $1600, which includes both user licenses and add-ons.

There are no additional costs beyond the licensing fees, and it covers support.

Before choosing this solution we evaluated SmartShift for work management, and we also tried Trello.

My advice for anyone who is implementing this solution is to ensure that your in-house processes are clear. Things have to be clear, as much as flexible, because if it is not correctly configured then it could just be a mess. So, you have to be very clear on what your processes are in-house, and then based on that you can translate them into Jira.

Knowing in advance what kind of information you're looking for from Jira will help you in being able to set it up correctly.

I would rate this solution an eight out of ten.

In terms of requirements management, the ability to write the descriptions and acceptance criteria are helpful. We can also group the stories by epic and associate stories by themes. There are tags that help us categorize stories. We can attach documents such as use cases and spreadsheets for detailed information as well as link to other stories.

We are able to track the development work for a particular story or set of stories through the Kanban board easily. The tool helps with team collaboration and raises visibility to the backlog of work to those who are interested in the project’s requirements.

We spend hours and sometimes days looking through completed stories in order to determine how to manage a defect in our existing system. We used to use Word and Excel for requirements documentation, and thought primitive, still, I was able to find specific requirements for just about any topic in a matter of minutes by using various searches and by simply knowing that a requirement probably resides in a specific document. I would ask that Altassian improve its keyword search capability and provide reports that could group information in the way I want it grouped for re-use by maintenance and production support teams when troubleshooting an existing system.

We've used it for three years for managing the product and sprint backlog of our agile projects. The product was never designed for requirements management yet our organization still insists we can and will use it to manage requirements. We considered some add-ons to the product but so far.

I am not aware of any issues with the deployment.

I am not aware of any issues with the stability.

I am not aware of any issues with the scalability.

From what I can tell the technical support is adequate. I do not deal with Altassian so I cannot provide a valid answer.

I was not involved in the decision to use this product. Our Product Owner team made some recommendations for add in products and stand-alone ones; however our recommendations were rejected due to cost considerations. Previously we used Excel, Word and Visio to represent the requirements. We stored the documents in a common share and versioned the documents each time changes were made.

We have a complex implementation. I do not know if the initial set up was straight forward. We have many, many teams across the country using JIRA. Since we have a single implementation used by all teams. I can see all the projects and the stories etc. by logging in with my credentials.

Coming from projects that rely on Agile / SCRUM, one of the essential features in JIRA is the support for these methodologies, represented by the Agile Board functionality. This is the place where our team interacts with JIRA as part of the daily routine by updating tasks, estimations and adding relevant comments. This is also where Sprint planning takes place and where support for Sprint retrospective and analysis is offered in the form of reports like the burndown chart or the velocity report.

With the introduction of Agile, the need of having a common, synchronized view on the project tasks assignment, their completion status and the effort spent became critical for a geographically distributed and self-organizing team. Instead of spending time on e-mail exchanges or longer meetings, JIRA provided instant access and a unified view to all the required information, enabling the team to properly apply the Agile / SCRUM methodology and become more efficient in the way they communicate. Being instantly notified when an issue is changed by someone working half way across the globe and being able of giving immediate feedback is a tremendous capability.

I would like to see JQL extended to return other types of information than just sets of issues. To give a simple example: a COUNT-like operator to determine the number of issues that match a given criteria. Today this is possible through JIRA's REST API or by writing custom plugins, but it would be nice to have it out of the box directly via JQL.

I have been using JIRA for more than two and half years in several different software development projects.

None so far.

None so far.

None so far.

Customer Service: I actually found all the information I needed on the Atlassian documentation pages and forums and never ran into the need to call the Atlassian customer service.Technical Support: Excellent so far, considering the fact that the existing documentation gives almost all the required answers without the need to call or e-mail support.

In a previous project we have used Microsoft's .NET framework and the suite of support technologies like Team Foundation Server (TFS). TFS contains an issue tracking system fully integrated with Visual Studio and the only extra thing needed was the equivalent of an Agile board. This we found in the form of Telerik's TFS Work Item Manager and Project Dashboard, which offered similar functionality to JIRA's Agile Board.

The initial setup required a bit of thinking on how to organize and when to use the different types of JIRA issues, what fields are relevant in the context of our team processes and what kind of dashboard information is required, not only for the team but also for the stakeholders. This is not so much JIRA related as it is process-related. Once all of this is agreed upon, JIRA makes things easy by selecting for example Agile SCRUM as methodology, configuring the appropriate issue screens and workflows, defining the relevant filters and adding widgets to the dashboards.

I believe this goes together with my earlier comments. The day to day cost of using JIRA is minimal, since each team member shares the responsibility of keeping issues up to date so that the overall status is in sync with the real project status. There are also the occasional changes to JIRA board, issue or dashboards configuration driven by the evolution of team processes, which is a normal consequence of being an Agile team.

I recommend JIRA Agile to anyone looking for a mature, easy to use and customizable issue tracking system, especially in the context of large, geographically distributed teams. I also believe it is important not to spend excessive time trying to configure it to cover every process and situation from the very beginning, but to focus on the essentials first and then adapt as the project evolves.

We mainly use Jira software, including Jira Issue Manager, for bug tracking and project management, and have done so for over a decade. Then in the last six years we have also used Jira Agile in a lot of our project management work. We use the enterprise version of Jira.

There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training.

The simplicity of Jira is the part that I like the most, as well as the way in which it can be extended. For example, I like that you can send data to and from Jira easily, and it integrates well with lots of third-party plugins.

In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful.

When I first started using Jira and we were in the middle of coming up with a solution, I found that there could be better separation of tasks when it comes to user stories and epics. For example, right now we can take users and sub-task them, but the developer is not able to easily ask for or request a task as a separate thing to work on.

Other than that, I would definitely appreciate more kinds of features in general. But we have already requested these from Jira ourselves with their voting system. These requests are in their backlog now and we hope to see them in future soon.

We have been using Jira for more than ten years.

I feel it is quite stable, not least because it has been around for a long time. For the last few years, we have never see any issues from our location or any other location that our people use it from.

We have never had to use Jira's support as far as I know. 

I wasn't fully involved in the initial enterprise setup of Jira, but I remember first trying out some of the plugins on my laptop and I found it all rather easy. And for the people in charge of the main setup, they were able to install it and set it up quite fast.

We are using the enterprise license which is nice because it ensures that we always have the latest versions of Jira software. 

I would definitely recommend Jira for project management and similar uses, as well as other products from Atlassian like Bamboo.

Jira isn't what you would call a "coded solution" for scrum or anything like that, but it's able to do a lot of different things for people who are looking for that kind of thing. If you are looking for a custom-made solution specifically for agile or scrum, then you can go try other products like Valley or others. But if you want a good general-purpose project management system with solid integration solutions like Bamboo, then I think Jira is the product for you.

I would rate Jira an eight out of ten.

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

This software is implemented in the different departments of the company since it allows us to plan, organize and verify or monitor the different projects we develop day by day, thus improving communication and workflow.

The implementation of JIRA in the different business departments has allowed us to increase labor productivity since the teams work much more efficiently thanks to the tools provided by this powerful platform, which has made the communication much more specific and better. And when planning any task, the whole team is aware of every detail.

The most valuable features or functions that I have found in this software are several but mainly that it is a platform that gives the user the option to customize its interface to the point that it can be fully adapted to the team that implements it. This generates a great advantage since it is much easier for users to adapt to it and be able to work in a much more comfortable and highly effective way, in addition to providing tools that can be followed up on tasks or projects and give priority to them. It is really useful because in this way the team can focus on those who need a much closer delivery date.

This product or software still requires improvements, especially in its interface since its learning curve is somewhat high because it offers so many features that the user tends to get confused, or the software adaptation time is much longer than it should be. Besides, its configuration is not very simple, and its support team sometimes does not respond immediately, so it is often necessary to solve problems on their own.

Less than one year.

Although it still requires many improvements, it is a software that is kept updated to ensure that its users can be much more pleased when using it.

Its scalability is somewhat limited since it is based on the number of users, and when wanting to obtain a greater number of users, the prices are somewhat high.

Their customer service sometimes tends to fail because problems are not attended to immediately, but it is something that is not consecutive. But nevertheless, I believe that in an emergency this could bring problems.

We have not used another solution previously.

The initial configuration was complex because it is not simple, and that's because the software does not provide enough information to understand it.

It was initially implemented by the suppliers since it is somewhat complex and the team was not yet ready to perform it, but they had a really positive performance.

The investment has been fair since we have obtained advantages from its implementation, mainly because productivity has increased.

It should be very clear about the plan that you want to implement and what number of users will use it. In this way, you will pay for what you really need and will cover your needs since this software is based on the number of users implementing the same plan.

We did not evaluate other solutions.

This software is ideal for tracking problems, managing, planning and carrying out real-time monitoring of the tasks or projects you want to develop in a much simpler way and in the shortest possible time. So I think that if you are looking for a solution that is based on more than the management, this is the indicated choice.