Jira Reviews

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.

It's scalable.

It's easy to deploy.

The cost of the solution seems to be reasonable. 

Once the solution is deployed, it's not easy to configure. If you have a lot of capability, it's very dynamic from the back end. Therefore, when setting up the workflows, it can be a little bit complex. We did a lot of functions on managing the development and that's why maybe it's a little bit complex. Basically, in order to design a workflow in Jira, it's not a straightforward task.

From a feature perspective, not much is missing. However, they need to put some investment into the user experience. It needs to be easier to use, more friendly, especially on the configuration part. It's a hassle. You need to deal with a high learning curve in order to understand how it's configured and how it can work.

We've used the solution for more than eight years now.

The solution is scalable. 

We have more than 50 people using Jira at this time. 

We do plan to increase usage. We are growing. Since we are growing, we are increasing Jira as each member on the technology team needs an account for development, business analysis, or testing.

While the initial setup is pretty simple and straightforward, handling the configurations and the workflows can be complex. 

I didn't attend this in the development phase. In testing, I did the same effort and it took me a month to set up while I was deploying a test stream. I worked on the testing workflow as well, the defect workflow. That said, I don't know how long it takes for them to configure Jira.

We handled the setup in-house.

The licensing is per unit. My understanding is that it is pretty affordable. However, I don't directly deal with licensing.

We are just a customer and an end-user.

From a testing point of view, I would rate it at a six out of ten. I use it as a defect management tool, and it, for me, it's not easy to use.

Some of the use cases are for tracking issues and bugs.

I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.

The solution is deployed on-premises.

The solution is valuable because it's pretty flexible. It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company.

The solution could be more user-friendly.

I have been working with Jira within the past year.

The solution is pretty stable.

The solution is scalable. There are a few dozen users using this solution. We might increase the usage in the future.

I previously worked with ClickUp and would suggest using it. It's a competitor to Atlassian Jira.

When it comes to functionality and usability, I think ClickUp is better, but compared to Jira, ClickUp's drawback is their integrations with other products. The product is not old enough to be mature.

Jira is more flexible and more integrative with other products, and ClickUp is more user-friendly. The functionality is pretty rich.

I would rate this solution 9 out of 10. 

The only thing that I'd like to advise is to just monitor the market and keep an eye on comparison between the Jira and ClickUp.

We are using it to organize most of our software development processes. 

Being a cloud solution, we usually have the latest version, but sometimes, we get a pop-up saying that there are some changes in a menu or some new features are there.

It covers most of the development process, and almost everyone uses it. We are using it for every role involved in the project, such as business owners, product owners, testers, developers, and DevOps. For example, the product owner defines a new feature, and then we take the feature and create stories and development, testing, or DevOps tasks. We then implement the new feature or changes to an existing feature. All the test cases and other things are in Jira. So, everything is done in Jira.

It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days.

Its search and reporting can be improved. They are already nice, but they can be further improved.

I have been using this solution for more than 10 years.

Its availability is great.

We have different offices, and overall, there might be about 2,000 people. There are no issues with its performance or service. Almost all roles in our company are using this solution.

Other people have experience with Jira's technical support, and they are quite happy with their support. Personally, I never had a case where I needed any kind of support.

It is a cloud solution. It just requires licensing. Of course, some support would be required for all users of Jira, which could be in thousands. It might not be an easy task, but overall, I don't think a lot of time is spent on its maintenance and support. It is a very trustworthy service.

It is certainly a long-term solution for our company and for previous companies that I have worked for. They have these long-term term licenses, but I'm not sure if they really pay on a yearly basis. They are certainly using it for a really long period and for a lot of users.

I would definitely recommend this solution. It is very popular, and a lot of my colleagues have used it before. It doesn't require a lot of learning time. It is very good to use. I'm quite happy with the service. Of course, it can improve, but personally, I'm very happy with it.

I would definitely give it a good rating. I would rate it a nine out of 10.

We use JIRA for the management of tasks in IT. We are in the process of implementing our JIRA service desk and using other software for development, such as Bitbucket.

When combining Jira with Bitbucket, you have the possibility to ensure continuous integration and other functions which is highly appreciated by our software development team.

I have been using Jira for approximately three years.

Jira has been stable in my experience.

The solution is scalable. The new licensing model that was presented to me for the data center oriented solution, the price tag that comes with it is the equivalent of 500 users. I only have 50 to 60 users, which means that I have to multiply my budget by 10. This is the scalability that they should be able to provide and I do not like that too much. I can accept that there is a markup for the data center but not the way they have currently presented it.

We will have approximately 60 people using the solution and when it comes to the software development team there are approximately 100 users. It is used in two separate environments.

I have not contacted technical support personally.

Before we used Jira, our operations were very Microsoft office-based.

I am not a regular day-to-day user of this solution and based on the feedback that I received from people at the time it was installed, it went well.

We have one person from an external party who helped us with the implementation. For the internal technical deployment, we have approximately five people from different teams in infrastructure, help desk, and application.

The price at the moment for Jira is okay. I'm absolutely not amused with the plans to try to drive us to the cloud or to other licensing models. For the very simple reason that we are a company in the defense sector where cloud is problematic in a number of the domains. We are now approximately 60 users and the new policy will actually confront us with an upscale to approximately 500 users. I find it unacceptable, and may potentially lead us to look for another solution.

They need to think about industries, which are for compliance reasons are not capable of moving to the cloud, and that they don't put a knife on our throats with excessive prices.

For my defense software development activities, I would like to stay out of the cloud. For the general industry activities and the IT support, we could potentially go into the cloud. There is no objection to that. But for defense, the cloud is not an option for me.

If you want to move ahead to the cloud, I would definitely recommend Jira. For what we use it for since we are stuck on-premise, I would advise others to look into other solutions.

I am not an active user of Jira but based on the feedback I have received I rate Jira an eight out of ten.

I'm head of the IT service desk, and we're using it to track IT tickets from the users. If there is an incident or someone requests information or services, we handle all these requests through Jira Service Desk.

Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes. I'm the IT service manager, so I'm like the director. A cleaner interface helps my team stay on top of the service requests. We used to just take requests via email, and we had some kind of old IT tool, but it wasn't as effective as Jira. And because we are connected to Power BI, we have better visibility. You have a range of metrics so you get some good insight when you integrate Jira to Power BI.

My colleagues started dealing with Jira in 2019, and they're still using it. And my team implemented the Jira Service Desk in 2020 because the rest of the company was using Jira.

Stable. What about scalability? Is it scalable?

We get outstanding technical support through our partner Valiantys, which is a French Jira distributor certified by Atlassian to resale Jira.

It's not a complex implementation, but it's not easy either. I think it's somewhere in the middle. It's an average software implementation.

Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper. And now they are making us move to the cloud. They gave us a deadline to migrate from the on-premise Jira Service Desk to the cloud. It's been two years since we started using it, so I think we will get a discount.

I rate Jira Service Desk seven out of 10