Jira Reviews

My primary use case is using the boards in working stories for freeing up the backlog and assigning tasks to my developer team. 

No other stats of graphics or reports from Jira are used. We use Grafana instead of that.

I really enjoy the easy way I can follow up the story's progress even when they are in progress or we test bug stories. When issues arise, they can play back to the team in order to fix all the bugs. They have a view of the backlogs in the current sprint and the next sprint. 

The initial setup is straightforward. 

There are many Jira add-ons available, however, we aren't using those yet.

The solution is stable.

We've found the scalability to be good.

I alternate Jira with Excel. I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira.

I've been using Jira for about four years. It's been a while. 

The stability is quite good. There are only some updates that are made by IT, however, it's working fine for me. I haven't dealt with bugs or glitches. it doesn't crash or freeze. 

The solution is scalable. I've tried other solutions, and this one seems to be the most adequate for my needs.

We have about 1,000 users worldwide. There are several projects running in several parts of the world. 

We do not plan to increase usage. We are using it as we need it and no more than that.

We've never faced any big issues and we have never had Jira go down. Therefore, we've never had a need to contact technical support. I can't speak to how helpful or responsive they are.

I found the initial setup to be pretty simple and straightforward. It was not an overly complex process. 

However, largely, we are just testing Jira. I can't speak to how long the deployment takes. 

I have three teams that can handle deployment tasks. There are six people in one, seven in another, and ten in the third one.

We do not use resellers or integrators to assist with the initial setup. We can handle the process ourselves.

I don't have any information in regards to the licensing or cost of the solution. It's not an aspect of Jira I handle. 

I have tried or tested other options such as Excel, Monday, Trello, Tetra. In comparison, for how I use it, Jira is the most adequate for my daily job.

We're a customer and an end-user.

Nowadays I'm using the web version of Jira for my client. I'm managing my boards, my sprints, and my backlog which are all working on Jira except the retrospectives. These are made in a code and not written down in Jira.

I would recommend the solution to others. It's easy to learn, easy to handle, and we've never experienced any downtime for a year and a half at least.

I would rate the solution at a nine out of ten. I haven't fully utilized the entire product, however, from what I have seen, it's exactly what we require. 

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.

We use Agile Practices, so we track all our projects in Jira. When the project starts, we start putting all the user stories there. If any user story has any down the line task or user career task, we attach those Jira stories to our Confluence pages as well. So we maintain Confluence pages as well as Jira together as a story. The requirement and the Jira story are linked together.

Managing and keeping track of projects is a little bit difficult in the IT world. Jira provides the exact picture of where a project stands. It also provides automation or DevOps technologies. This brings our company together, and whenever we have to see a project's exact state, we can use Jira.

It's a Scrum tool, so it's very easy to use. That's what I like about it.

You can very quickly create a new project, add stories, and then make them into a sprint. It's very user-friendly.

Jira covers everything for project management and life cycle related items. It's a fine tool to work with.

I have not seen any issues with stability or scalability.

Sometimes, it gets a little bit difficult to find the exact issues for people, but the search works fine in general.

The Classic UI is a little bit messy. UX experience is also a little bit messy and is not according to the expectation of a tech user.

If I click on an issue, that issue opens on the side. It shouldn't be like that; either it should open as a pop-up so that I can see where it is opening or it should open somewhere else, maybe as a pop-up or a new page. The view on the side is a bit of a hurdle. The UX needs to be improved.

Good use of Kanban technology should be there. Right now, it is mixed with Scrum technology, but that's not very necessary.

I've worked with Jira for more than five years. Our company has been using JIRA for a long time.

It is stable; I've never seen it down.

The scalability is also good. We are a company of more than 800 people, and I haven't seen any scalability problems as of yet.

Most of the users are developers, and at least 700 users must be using Jira in our system.

I think the starter pack of three users, up to five users, is free. So you can try it out.

In terms of project management and repository management for the code, I find Jira to be the best. So on a scale from one to ten, I would rate it at nine.

We use Jira for task tracking, sprint planning, and backlog.

The dashboards are useful. You have visibility across projects and various dashboards.

The status of the different activities is also helpful 

In general, it is not user-friendly. 

For a non-technical person to use, Jira is not intuitive. If you are a developer it's fine, but we are trying to get other technical people in to look at tasks or to update a task, move it from one sprint to another sprint and it takes more effort than I would like.

I would just like to see it easier to use, and I would like the workflows to be less complex to do what we need them to do.

My experience with Jira is limited, but the organization has been using Jira for three years.

We are using the latest version.

Jira is stable. to my knowledge, we have not had any issues with bugs or glitches.

The scalability can be complex if you are using workflows.

We have approximately 20 developers and some managers in our organization who use Jira. 

I have not yet used Jira technical support.

Previously, we did not use another solution. We started with Jira.

Along with Jira, we use Microsoft Azure DevOps.

The initial setup is fairly straightforward. 

It was fairly simple for us.

I would recommend getting sound knowledge first. It is difficult to go back later to fix things, so try to build it right the first time.

For the functionality that exists, I think that it's good.

I would rate Jira an eight out of ten.

Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so.

We regularly check the tasks assigned to us, day by day, and create a work log in that task according to what has been done.

You can check today's task assigned to you by using a custom filter, which you can create on your own. We can also make a customized dashboard user-wise.

Upper-level management can analyze the chart and get an overview of the project, giving them the ability to estimate the budget and release date of the project.

After purchasing Jira, we started shifting to it from the older software we used, like Bugzilla. Bugzilla was being used as our bug reporting tool but after the introduction of Jira, we began to use several of its features. We now use Jira for Scrum Planning, Bug Reporting, Time Tracking, and Budget Tracking.

Day by day, the transparency of the project improves and estimating the project release date becomes easier to do. It is also easy for management-level users to check the project's budget and estimate the release date for a specific feature.

Because there are a number of charts available, looking at them will assist you with any decision that is related to your project.

As a user of the Jira, rather than an administrator, the custom dashboard and custom filter are some of the best features from my perspective.

I can manage my own dashboard and by logging into my account every day, I can get information about the day's tasks assigned to me. I can also see my timeline chart, and using that, I can see and understand what has been done in the last week/month.

I have added a gadget on my dashboard that gives me regular updates on the bugs reported by the QA team.

Jira is one of the best software applications for project management and budget tracking, but it does have some issues, as follows:

• Firstly, the filtering feature can be improved to some degree.
• Because JIRA has so many features, it may take some time to obtain a general knowledge of each one.
• In order to enhance adoption in small and medium businesses, the cost should be improved.
• I believe it will be difficult for new users to understand.
• There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported.

In our organization, we have been Jira since 2017.

Previously, we were using the Bugzilla bug tracking software for reporting bugs from the QA and FITs. Due to the number of problems that we had with it, we purchased Jira and have been using it for approximately five years.

The initial setup was easy, and we haven't found any difficulty in that.

The pricing is much higher than other similar solutions available in the market, and as such, the vendor should think about a price reduction to make this product more affordable.

We did not evaluate other options before implementing Jira.

Virtually every day we have our daily scrum. Our team gathers around the board, which has all the columns showing where the tasks are standing: requested, planning, ready-coding, review, etc. Together, we view one task after the other and update the statuses. It's really a focal point of the team to know where the work stands, and what's the progress of the work since the last time we checked.

Within my company, there are roughly 25 employees using this solution. We have a scrum master, who's the most knowledgeable person on the tool. usually, they're the ones organizing the tasks, creating new tasks, and then creating the report at the end of the sprint or the quarter. They're the person who's creating the reports, using the more advanced features. That's the scrum master.

There are the developers, including me as a tech lead. There's the tester. There are managers — once in a while we have to present them with some reports and statistics, so they know how much work is being achieved, but they don't have in-depth knowledge of the tool. It's really an internal tool, so the customer is not involved.

We're not expanding much at the moment. We've been expanding in the past year, but now things have slowed down a little bit due to COVID-19.

With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board. Nothing gets forgotten — it forces the team to make a decision on every little task that is planned.

The way we can quickly see in which state a task stands — with everything classified by columns. It's easy to know who is taking care of what. For instance, if I want to know how busy the person in charge of QA is, I can easily see what staff members are working for him via a little face icon or a tower. I can see who is responsible for what tasks. The board gives you a quick summary of the workload of everybody on the team.

When a task is completed, it disappears and I don't know how to find it. If I want to go back in history to review an old task that we completed, I cannot find it. Unless you remember a keyword or a task number, it can be very difficult to find old tasks.

Sometimes, in the display, there is an overload of information that makes it very difficult to read. If there's too much information, it defeats the purpose. You have to reach a balance, and I think at the moment, there can be too much information.

Sometimes the interface is too crowded. It seems like the default option when you open a task is that everything is open and all of the menus are deployed.

There needs to be easier integration with third-parties — personally, this is the biggest issue for me.

I have been using Jira extensively for one year.

Atlassian tools from the Atlassian suite are all linked together. We use GitLab. We wanted to integrate GitLab with Jira because whenever we create a branch in GitLab, for a repository, we create a branch to develop a feature or to fix a bug. Once the work is done, we have to merge that back into the master branch. When we do the merge, we name the merge and we enter a reference to a Jira issue.

It's easy after that. The person who's taking care of and viewing the merge requests can just click somewhere on a piece of information in the merge request, and it brings you to Jira, to the associated tasks. Usually, for each task, we end up creating a branch; it gets reviewed and merged back into the master. Once the review is done, it's ready to be tested.

That's our work procedure. Basically, the two tools — GitLab and Jira — need to be integrated with each other, but at the moment, there is a bug and It doesn't work. IT reported that problem to Jira or GitLab, but we have not heard back. 

There is a problem when it comes to integrating Jira with other tools, or other tools with Jira, there seems to be a weakness there.

Adding more users is not a problem. We haven't tried to add a third-party or to integrate with a third-party, so I can't comment on that. 

We don't tend to use Jira outside of its purpose at the moment. It's hard to answer this because we just add or remove users; we're not trying to upscale it to a higher scope or anything.

I go through IT for technical support. Except for that problem I mentioned, the integration between GitLab and Jira, we tend to find the answers pretty quickly.

Jira offers good technical support.

I didn't help with the initial set up myself. Since we have web access, you don't have to install anything. It was already installed when I joined the company.

Our IT team handles all maintenance-related issues. They don't necessarily know all the menus of Jira, all its capabilities, but they know how to deploy it.

Have a training session before you begin using it. That tool is good for teamwork, but it doesn't replace a face-to-face discussion. Among yourselves and your teams, establish some conventions as to how you will describe your tasks — what criteria will be acceptable? Include a section for requirements, have a section dedicated to discovering your setup because the tool has its limits. It helps you organize your work, but it doesn't replace the self-discipline of the developers to stick to some team conventions — that's also really helpful to get the full benefits of that tool.

One of the main advantages is that everything becomes visible when you use this tool. When your work is done in full daylight, it's difficult at the beginning because you feel like everybody's looking at what you do — it's all visible. They can access the information through JIRA, but at the same time, you're not going to get stuck too long in your corner. The drawback is that you feel more like you are being spied on. It feels like you're working in an aquarium. Everything you do is visible. But at the same time, you're not going to get stuck on your own. Without this tool, it's easy to get stuck on your own.

There's room for improvement. Sometimes the window is too crowded and the integration capabilities need to be improved. Overall, on a scale from one to ten, I would give Jira a rating of eight.

Easy to configure, very fast to configure, extremely powerful workflows and schemes, integrates with other Atlassian tools as well as 3rd party tools.

Collaboration and software development lifecycle were the 2 keys that JIRA served great for. We have multiple organizations in the company already using JIRA for tracking projects.

Better JIRA Agile integration and more functionality related to JIRA Agile plugin

JIRA: 10 years

We didn't encounter any deployment issues

We didn't encounter any stability issues

We didn't encounter any scalability issues

9/10

8/10

Remedy, Bugzilla, Clearcase, TestTrack and Rally have all been replaced with JIRA with my leadership

Straightforward

In-House

60%

10 years ago 2K initially and 1K for additional plugins. recently 10K for the Atlassian Suite and additional plugins.

HP QTP, Serena Business Manager, Rally

It rocks simply.

JIRA features are agile planning and release notes. We heavily use the Service Desk to support our product customers, and we also provide support for our services customers via JIRA tickets with a time tracking plug-in so invoicing, project status, are available to everyone us and our clients, keeping us on the same page.

We are now using this system for all time tracking of internal non-billable projects, support contracts, development tasks and billable work. We can see our resources utilization and track how much time was spent on each client, which is good for invoicing, on Go2Group made products. This helps with our ROI on a product by product basis, and we even track our time off in this system.

It has enabled us to be on the same page with our client’s they can see the tasks and burn downs and exactly where their money is being spent. When we combine this with the Confluence Wiki, we now have a very robust Q&A and documentation page. We use it for sign-offs and online documentation. There is a history of what folks have done, and the information is radiated out in near real time. It is all there.

We can serve multiple clients, our own internal products, projects, and operations from one system cutting the resources needed to run these systems. Compliance is much easier to achieve, documentation, you need to sort out what needs to be displayed and reported in the formats you wish.

All in all, these tools, with little effort or cost, have allowed us to provide, what larger consulting and product firms struggle to provide due to legacy products/system/acquisitions, and compliance.

A more enhanced Service Desk module, with support for more types of alarms and the like.

The product is very easy to download, and install. Once downloaded, you just click next, OK, then viola! You are a newly minted JIRA Administrator, it is too easy. Teams, company data, and processes end up growing from grass roots movement before management realize it.

While Atlassian and TFS seem to be more of the toolsets that companies are adopting, and they are great core ALM stacks to build upon, you are still going to need tools from other vendors for most environments. For instance, you have more strenuous support desk needs, there is ServiceNow. If you make cars, boats, aeroplanes, trains, etc., you will most likely need IBM Rational DOORS. High end testing is still the domain of HP ALM/QC. Aerospace higher-end agile planning, you could look at JIRA Agile or VersionOne, or Rally. Embedded C, etc.

To summarize, MS TFS and/or Atlassian (maker of JIRA) are good core ALM stacks to run your shop on. The remaining issues are generally around how to integrate other systems to TFS or Atlassian, and also, how to migrate to TFS/Atlassian.

We are a heavy user of the Atlassian tools and are a reseller. We do VAR work for other competing ALM solutions as well, notably Microsoft, IBM, HP, Perforce, etc. This is just the toolset we have grown into.

Then they look into the systems and realize what risks there are and are usually slow on the uptake to designate these systems as Class A or B critical systems. They may be surprised at how many individual systems have sprouted across their organizations. You can find yourself in an organization with multiple JIRA instances due to the grass roots nature of adoption, with dozens of workflows and hundreds of custom fields in each instance.

It can be a lot of work to pull these together under compliance and DevOps. Would be much easier to accept these tools as mission critical, or at least realize their importance, and grow them correctly.