Jira Reviews

Multiple features make this product a delight to use. Using this for backlog prioritization is the key to either kanban or scrum processes. JIRA does a great job of articulating the story and adding elements to the story to help in the prioritization. If you are overseeing multiple projects, it allows you to easily follow the teams progress.

Another feature is the ability to incorporate add-ons. It’s great to have for those one-off processes you need. For example, the integration with Confluence.

Working in a dev shop that is 100% scrum, this tool is invaluable in its insights to how the process is working. Are the stories written well? Is the team executing on the highest priorities? How is the team executing sprint by sprint? All these can be found easily within JIRA, either with their out-of-the-box reporting, or the ease with which search queries can be downloaded to CSV to manipulate in a data visualization tool.

The reporting out of the box is minimal; I would like to see a report-building capability out of the box. Teams have access to more than a dozen out-of-the-box reports with real-time, actionable insights into how their teams are performing sprint over sprint. Examples include Burndown, Sprint, Cumulative Flow, Epic , release, Velocity. However most will find these reports too simple and want some sophistication. Luckily Jira gives the ability to export results where you can work offline with them in a tool like Google Sheets, Microsoft Excel or other preferred data parsing tool. For additional spend you can purchase their reporting plugin.

I have used this application for approximately five years over several different roles: product management, development manager and delivery manager.

We deployed on premise. The amount of time to deploy was simple for a trained technician. Would highly recommend if installing on premise to shy away from any customizations in workflows; will make upgrades a pain in the future. If you considering using this, I would recommend the cloud option first.

No issues with stability.

Like any application installed on premise, you must be monitoring server and application logs to ensure the right level of performance. Scaling up is easy.

Most of their customer service comes from the community. Robust community of evangelists who respond rather quickly. As the application is highly stable, contacting customer service has been few and far between. Responses came thru within expected timeframes and were helpful, even if pointing to already published articles.

I would rate their technical support high.

I've also used Microsoft TFS (Team Foundation Server) for another development team that was .NET based. Used both Jira and TFS at the same time, though for different project teams.

Atlassian built their reputation on building applications that were easy to install and using a community model to improve. The setup of JIRA was straightforward, just as the documentation indicated. Us technology people have a hard time reading thru user guides, but these were easy and quick.

It was implemented by one of our developers.

Development teams, especially scrum teams, need some type of tool. For geographically dispersed teams, the ROI has a quick payback period, less than three months. Geography could be the dev team in one city and the product team in another.

Look to their cloud offering first; get using it quickly. Be wary of some of the add-ons, as there are cost components to them; if you need them, add them in.

As indicated above, we used Microsoft TFS. We tried to have a JavaScript team use TFS, but it didn't really fit into all the other ALM tools a JavaScript developer uses, so we quickly scrapped TFS and moved back to JIRA. The same was true for a .NET team; tried to have them use JIRA, but it was difficult to break the Microsoft eco-system. Not impossible in that case, just a culture shift you want to address carefully.

Review all your use cases for the tools to see if Atlassian matches up nicely to those you need; makes integration easier when all are from one provider. Be sure you understand what you are licensed for and what costs extra. For example, do you need portfolio management? Because, if you do, it's an extra cost.

I use Jira in my company as a project management and software development tool. We use Jira in our company to document all of our requirements and releases in relation to project management and manage the agile lifecycle management of our products.

The most valuable feature of the solution is that it is easy to use and allows users to use agile methodology. Jira also offers a lot of plug-ins, which are helpful.

I would love to have more free plug-ins in the solution since most of its present plug-ins are great. I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting.

I have been using Jira for four to five years.

It is a stable solution as it is a cloud-based product.

It is a scalable solution, but it comes with an extra cost.

More than 100 employees in our company use the solution.

My company has not faced any problems or issues with the use of the solution. That tool's use can be easily extended.

As everybody in the organization has a role in the use of the product, employees ranging from managers to developers use it.

My company has not faced issues with the use of the solution. It is very easy to reach out to the technical support team of the product if our company faces any issues with the product. My company just needs to schedule a call with the technical support team of the product, and they readily help us. The solution's technical support is good.

I have worked with some other tools in the past. My company chose Jira since it was easy to use, scalable, and pretty straightforward.

The product's initial setup phase was straightforward.

The product's deployment phase was straightforward, as one just needs an account to log in. As not many technicalities are involved in the product's deployment process, it is useful for project lifecycle management.

The solution is deployed on the cloud. Jira also allows users to opt for an on-premises deployment model.

There is a need to make yearly payments towards the licensing costs attached to the solution. The product offers flexibility in pricing since it depends on the memory bits you have used.

It is a perfect tool for those who want to manage the projects in their organization.

The benefit I have seen from using Jira is that it streamlines the development process. In general, the solution provides visibility and streamlines processes.

I rate the overall tool an eight out of ten.

We use Jira for project management and tracking. 

I want the tool to integrate connectors. 

I have been using the product for five years. 

Jira is stable. 

The solution is scalable. My company has 300 users. 

Jira's deployment is easy. 

The tool's pricing is reasonable. 

I rate the product a nine out of ten overall. 

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories.

We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is

going on.

When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

The monitoring, flexibility and tracking are really good in Jira.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

I have been using Jira for eight years. 

Jira is a stable product. I have seen the growth in the solution’s stability for the last eight years. The current version is quite stable and is a robust system.

Overall, the solution is scalable. Jira is quite easy to scale. If we have five projects working on Jira and we have about five more projects to be incorporated, it's easy to install Jira for those five projects as well. Presently, twenty five thousand users are using Jira. 

We have been using this for the last eight years and we are quite accustomed to that. We don’t need much support from Jira or Atlassian. Yes, but we have got an enterprise version of that, and their support is quite quick.

Positive

I was using HPE Quality Management Tool.

The initial setup of Jira is very easy. I have been an administrator, so I would say that because used to it. But in comparison to other systems, yeah, it’s quite easy and user-friendly. The deployment takes two to three days of time. Forty people are required for the maintenance of the solution.

I implemented it myself as an administrator of Jira.

Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end.

You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things.

I rate the overall solution a seven out of ten.

The solution allows us to escalate issues from the end-user customer very easily. For example, if they're trying to access our PayPal page, and they're getting an error, we will do the basic troubleshooting. If the problem persists, then we will file the case and we will send all the stuff to reproduce the issues, including the ID, everything, using the Jira tool. We will create the task and it will go to the Level Three engineering team. They'll create that bug and route it to the Product Development team. Since the time I've raised the ticket, there are lots of options and there are lots of products that we may be using. That includes understanding what is the issue, what is the SLA, what is the issue criteria, et cetera. We can create and submit issues based on multiple types of criteria.

I can collaborate on issues that I've escalated very easily, even if they were escalated to different groups. I can segregate as well. It makes it easy to track bugs and issues. 

My experience with Jira has been great. Jira can track bugs and records improvements clearly. 

It's easy to escalate the issues to the product development team. 

It's not that difficult to create and file an issue. It is very user-friendly.

The ability to include attachments and assign reporters is great. We're able to easily delegate the task. That's extremely helpful. 

In every email, there is a way to track who is looking at a specific issue. If you look into Jira, there will be a crystal clear communication chain from the start to end of any issue.

In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team. Or, for example, if you're sending a Jira ticket to me, I should get an alert if I've not worked on the ticket for a long time. I should always get an alert within 24 hours. For example, there should be three kinds of alerts. If a Jira ticket is raised and does not have any steps, for example, if I'm not assigned, it should be in green. If one day goes by, it should be in yellow. If the SLA is about to end, it should be in red. That way, I will know what needs to get attention. I'd be able to say "Oh, I should work on my task." There should be some color-coded alerts to keep me informed in a more visual way.

Sometimes I might get an attachment from the user through email that I need to download and save to my local desktop. What feature I would like from Jira is the ability to have an attachment field option open Outlook. Right now, when you click an attachment, you can only attach the items which are stored on your desktop or documents that have been downloaded. However, there should be an option to attach a file to a Jira issue directly from Teams or Outlook.

They should offer free online training courses to users. 

I've been working with this solution for seven years. While I joined the organization seven years ago, the company had already been using Jira for quite some time. 

The stability is good and the solution follows the agile methodology. We've never had issues with its reliability. There are no bugs or glitches. It doesn't crash or freeze. the performance is good. 

It's my understanding that the solution can scale. 

We have more than 5,000 people using the solution right now. They include IT specialists, product support, developers, product owners, technical lead, and architects.

I have not faced any Jira issues. I have not raised any tickets to the Jira team directly. It works very well.

The company may have previously used ServiceNow, however, as I recall, it is difficult to expand, and therefore the company has used Jira for quite a long time. 

I'm from technical support. I'm not a part of the development team and therefore have not helped implement the solution. Therefore, I cannot speak to how easy or difficult the process is. 

Jira maintenance is taken care of by the product maintenance team and the change management team. While we own the product, they respond to it. 

I'm not aware of the pricing or costs. It's not an aspect of the solution I deal with directly.

I am aware, however, there is a bit of a cost to do the online training.

We are using the latest version of the solution. 

You can use both cloud and on-premises deployments. Cloud deployments can be on various clouds, including Amazon, Microsoft Azure, et cetera. We are using GCP, for example. 

I'd rate the solution at a ten out of ten.

We are using Jira for ticket management.

The solution has helped my companies efficiency with managing tickets throughout the life cycle.

We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface.

The solution could improve the Agile reports. They do have quite a bit of reports already, but additional reports would be a benefit.

I have used Jira within the past 12 months.

Jira is stable.

I have found Jira to be scalable.

We have a few hundreds using Jira in my organization. They consist of developers, project managers, and testers.

Whether we increase usage of the solution depends on what each team wants to do. There is some level of common solution approach, but I don't know for sure whether this is the direction that everybody is wanting to adopt.

We had to reach out to their support a few times. The support was good, I did not have any issues with them.

The initial setup was not difficult.

We have an IT team that supports the solution.

My advice to others wanting to implement this solution is to utilize the SaaS solution unless it is required not to. Having your own instance running in your data center or private cloud requires your own staff and resources to maintain and upkeep. It can be quite time-consuming work. Unless you are invested in something like that, there is a benefit of just using a SaaS solution.

I rate Jira a seven out of ten.

We are using it for project management.

It helps everyone to be on the same page.

Its integration with Bitbucket, Confluence, and other related products that Atlassian owns is most valuable.

If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications.

It should have more Trello-like features. There are some things you can do in Trello, but you can't do them in Jira, which doesn't make any sense because Jira bought Trello.

It looks pretty solid.

It looks scalable. I haven't seen any issues.

It is being used extensively at the moment in our organization. Currently, IT departments are using it.

I have not interacted with them.

I wasn't around during the setup.

It has a lot going on. They own Bamboo, but right now, we're using Jenkins. 

I have used Azure DevOps at another company. I would advise going for Azure DevOps because it has everything. You've got your DevOps, and you have your Repos. Everything is integrated.

I would rate Jira a six out of 10.

We use Jira for multiple uses; project management, task management, and we are starting to use it for release management.

The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on. For these results, it is very helpful. I also like the customization that we had for the workflows for the different issues, it's quick and easy to customize. The reporting is also easy and the dashboards that they provide are really helpful and simple. It does not need a lot of experience with reporting and presentation to get to what you need. Also, most of the advanced reports that you need to create can be exported as Excel files.

I have been watching an issue develop. There is a difference between their cloud and their  server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it.

Additionally, it would be really nice if they added some custom reports so that you could build your own report through any open source or commercial plug-in like Crystal Reports. That would be much easier for them to accelerate. You can create a report template and use it frequently.

There are a few features I would like to see in the next release. For example, the layouts could be easier to configure on the screens. I know it's easy to customize. For each issue type you can create and modify your screen. But it would be easier if you could enlarge, copy, clone, and visualize them in a model in a visual way. It's really hard for me as an admin to compare different screens or even to copy one screen with one additional field. I believe that is creating a lot of confusion for end-users because usually admins are looking at each field independently, where it's located, in which position, and which screen. So that all needs to be improved from an administration point of view to make it easier to visualize and compare between the screens.

I have been using Jira for almost a year now.

In terms of stability, it is fine.

The initial setup is easy and straightforward. The deployment is very easy. It just took one server.

It took one day to set up the database and then start the configuration. That is straightforward. And I believe they have a newer deployment model that they can deploy on Docker and other container platforms.

I did it myself with some help from other team members.

Jira is an amazing tool, but to get the process streamlined is a challenge. So don't start from Jira. Start with your process first. Agree on the workflow, identify all the stakeholders, and then from there you can go ahead with Jira and implement anything.

On a scale of one to ten, I give Jira a 10.

Everything already provided is perfect. We are using Jira perfectly for one year now and it's absolutely great.