Jira Reviews

<ul> <li>Ability to search old issues.</li> <li>Ability to create your own tags and fields, ie customization.</li> <li>Easy of use. I have trained several non-it people in its usage and they all say it's really easy software to use.</li> </ul>

Our development team and it's functional staff have gained a better overview of the issues that are being worked on and what issued are getting delivered in a patch.

Perhaps a built in "Jira-Capture"

I've used it at 3-4 different companies over the last 8 years.

None

None

Current company, only a small userbase of about 25 users. Previous company perhaps 150-200 users - no issues whatsoever. (We're in Norway, not many people here.)

Previous solutions ... did not work - to put it mildly.

Straightforward setup.

In House

Previous product cost us about 100.000 NOK/yearly (USD 15,000/year). JIRA costs us perhaps around 25.000NOK (USD 3,800) on time setup cost with all the plugins we've purchased.

Time spent setting things up. Perhaps one or two hours a week on average for one developer.

No, did not evaluate other options, as JIRA fulfilled our need.

Go for it!

We use it for project organization, workflow, and team collaboration. 

I like it for team collaboration and task management. I also like its analytics and dashboards.

It is easy to use. Our junior people find it easy to create tasks in Jira. It is intuitive if you've been using similar products.

Their support should be improved. They should be faster and more knowledgeable.

In Jira Cloud, integration with Excel is missing. Previously, I could import our Excel files into Jira, and I could also download a big Jira report in the Excel format, but now, it needs to be manipulated after that, which is not good. It looks like they've done that on purpose, but I don't understand the reason for it.

I have been using this solution for 10 years. I have used it in different companies.

It seems stable to me. 

It is scalable. It can cover many projects and a lot of job delegations.

We are a company of 2,000 people, but we all don't use Jira. All IT departments use Jira and Confluence together. They are always paired together because documentation is important.

Their support, in general, could be better. In my recent experience, people who were allocated were slow, and they didn't have the knowledge. They ask you to read the help and documentation about an issue and do self-service.

We also have Teams because it is given to us, but we don't use it because it doesn't have that richness, and it lacks the features that people need. It's very light for task management.

For me, it is straightforward.

We have a corporate license, and it is probably based on the number of people.

I would recommend this solution. It gives you the best if you investigate a little bit and maximize your use by using all the features.

I would rate it an eight out of 10 because of the support.

Public Cloud

We are using Jira mostly for the workflow dashboards for our projects. For example, for now, we are using the Kanban boards at team levels and also between team cooperation levels.

The links between tickets are very valuable and the boards I found to be configurable and usable.  The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use.

I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues.

I have been using Jira for approximately four years.

Jira is easy to scale. We are implementing it for our team and for other teams, such as the relations teams. If you look at the different levels, such as the coordination levels, we are using it extensively on a daily basis.

In my team, we have less than 100 users using this solution but we also have other teams in our large company that could be using the solution. Our company has thousands of employees.

I have not contacted support.

The initial setup of Jira is straightforward.

We have a team in my organization that specifically handles the support of Jira.

The stability and performance are good, I have not had any complaints from people using Jira.

I would recommend Jira to others.

I have not used many tools to compare Jira with.

I rate Jira a seven out of ten.

On-premises

I use it for portfolio countdown. I work as an enterprise architect in the company, and my usage of Jira is minimal. Software engineers in our company use Jira very heavily, but I do not use it for my day-to-day work.

Cadence management has improved with Jira bots.

Its visual display and ease of use are most valuable.

Sometimes, the status change is too difficult. The change of status is not configured correctly. We sometimes have a limitation on the number of changes that each workflow can do, so we get very restricted with the changes, and status change gets difficult. It could be specific to our implementation. 

Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done.

Color codes are currently missing in Jira. It is very limited in that aspect. I would like to be able to color certain impediments or features in red. I don't want to look at everything ticket by ticket. I just want to be able to look at the colors and see where we are. I am not getting that in Jira currently. Maybe it is there, and I don't know about it.

It is stable.

Once we moved to the cloud, it became better. Its scalability should be good.

We have more than 2,000 users. It is extensively used, and we want to use it more and more.

We never had a similar solution because we were a waterfall organization. After we moved to the Agile methodology, we started using Jira.

I was not a part of its implementation.

We most probably didn't evaluate other solutions. For Portfolio for Jira, we considered other solutions such as Planview or ServiceNow, but for the software engineering development life cycle, we probably didn't evaluate anything.

When we cut over to Agile, it was a huge task to get everybody on the same page in terms of the setup and rollout. When we looked at each other's desktops, it looked so different, and our central team did a lot of effort in making it all look the same. I saw the full central team being pulled forward to resolve these inconsistencies. 

It is so open that it allows inconsistency. So, you need to have a very strong and resourced team for the initial setup, implementation, and training. Otherwise, it can just fail. It could be a good thing that it is open, and everybody can have their own Jira, but finally, when the organization wants some statistics on what's happening at the enterprise level, you will not get any data. So, my suggestion to anyone cutting over to Jira is to have a very strong and resourced team centrally. You should roll out, learn, and come back to it. You should repeat this process and keep on learning and coming back. It has to be a very strong cycle.

I would rate it an eight out of 10.

Public Cloud

We are using Jira for requirement and defect management. Not for DevOps purposes, only application development.

The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features. Additionally, it is user-friendly.

The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again.

In an upcoming release, they should improve the user management features. For example, when I want to monitor a project as a CEO I do not want all the details but enough that I can understand. Additionally, these features should be accessible to me by mobile.

I have been using Jira for approximately two years.

Jira is a reliable solution for that medium-sized organizations. It's not for enterprise-level organizations, they have a long way to go.

The scalability has to be improved more because Jira currently is similar to a standalone solution with very limited integration. The integration with other products has to be more.

We have approximately 50,000 people using the solution.

We use our own IT department for the technical support of Jira.

The initial setup was complex.

We used to be on a perpetual license provided by our clients.

I would recommend this solution to others. Any new startup company can start with Jira immediately because it is now offered in the cloud.

I rate Jira a nine out of ten.

On-premises

We primarily use the solution for all issue reporting. The business uses it and we use it in IT as well. Any issue, anything from the help desk to software issues use Jira. It can house test plans, test sets, test executions, and provide some reporting. It's the reporting that's important for us.

The product has formalized the workflow process for reporting tracking and stacking and processing issues. It's also added some formal approvals, just for the purpose of formalization of a process workflow.

If you're using it in an agile shop, the traceability between epic story's test case defects is very helpful. 

I like that all of the team members on an agile team can use it. No one is in a separate application.

The stability is good.

The product can scale, so long as you have storage.

The reporting needs to be better. Being able to do some test management would be useful. In the tool, it would be ideal if they could give you some out-of-the-box reports for things like requirement coverage and regression and things of that nature.

I've used the solution off and on for about four years. I used it when it first came out to do some evaluation and we implemented it at a startup. That was when it first started. I've probably only really used it for about eight months on a daily basis.

We have had no downtime, and therefore I don't have anything to say that would be negative. It seems to be quite stable. There are no bugs or glitches and it doesn't crash or freeze.

As long as a company has the money for storage, it's scalable to any size. A small company can use it or an enterprise-level company can use it. It works for both.

Currently, we have less than 1,000 users in our organization using the solution.

Jira is extensively used in our organization.

We do plan to increase usage as well. The company purchased it so that it would be scalable. There's not a solid plan right now to add measurable users or increase the size, however, we know that it's available and that's what we were looking for - something that is scalable. The plans are to grow and as that growth happens, either organically, or via the purchase of other financial entities, we can grow the size of the database application and the number of the users.

I did not personally use technical support. I have worked several months with the people who have, and they say that the support is very good.

If the company used something previous to Jira, it was before my time. It possibly could have been Sharepoint, however, I was not with the company at that time.

The solution was implemented before I came to the company.

That said, my understanding is that the company tried to use as much out-of-the-box functionality as possible and it was quite an effort. They spent quite a lot of time formalizing workflows and things of that nature. In the end, it was very well thought out.

We do have a team for maintenance and what takes the most time with any upgrade is going through the changes, the enhancements, the defect fixes, and things like that. The actual time that it takes to physically update it is pretty minimal. However, going through the documentation and meeting with the team to make sure that we have testing covered prior to upgrading is work. We have a test environment prior to pushing it to production. That's what really takes time. It's not the physical update. An update might take two and a half hours and there's a lot of data in there.

My understanding is the company used professional services from Jira and also got some training and stuff of that nature.

We're just customers and end-users.

We just upgraded the solution. We are on the latest version.

I'd advise potential users to make sure that they talk to the people who are going to be testing and make sure that they know, what metrics they need before they pick a tool, any tool - even if it isn't Jira.

I'd rate the solution at an eight out of ten.

Private Cloud

Microsoft Azure

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.

Private Cloud

We use Jira to manage all our software development projects and our engineering projects. Our main use of the solution is for the workflows on our different types of projects. It's mainly used by our engineering groups, they have the proper workflows and all of the stats. As a director, I work more at the business level, tracking tasks similar to the new planner that's in Microsoft which some people are switching to. We also use it in the backend of the projects. For project managers and directors, it's more about a to-do list thing that's shared. I'm a company director and we are customers of Jira. 

The online collaborative nature of the solution has been helpful. Previously, coordination was done in Microsoft Project and Excel spreadsheets. The level of collaboration and the accessibility of the information which Jira offers has greatly improved things and we've also been able to build out and fine tune the workflows and the integration into the different tool sets. We're definitely going to keep using Jira.

I think the customization and tailoring of the workflows have proven to be very useful. And then there's the collaboration of the tool itself which has a lot of nice features. 

One of the issues is tracking the hours that people spend on each task. I know the solution has some built-in features but it doesn't quite meet our needs. We tried a couple of expansions unsuccessfully. Being able to track the effort on each of the tasks is important for us and we'd also like to be able to compare that with what's been budgeted. It would be useful. We've recently moved to Teams and some of the integration with Teams doesn't seem to work, whether it's not supported or not there, the ability to integrate that would be something we'd like to see. 

We've been using this solution for over five years. 

We haven't had any issues with stability. 

We're a fairly small organization. We've scaled up to around 500 users and we haven't had any issues with that. It's mainly used by our engineering group, and our active users use it all the time, on a daily basis. We'll increase as we organically grow. 

I can't recall the initial setup but it took us a while to figure out exactly how to use it. We deployed using our own staff. 

I don't know what the licensing costs are but we find them affordable. It's never been a major issue.

This is a powerful tool and allows a lot of collaboration, it's worth spending some time figuring out how your workflows will be, that's where the real value is.

I rate this solution an eight out of 10. 

Public Cloud