Jira Reviews

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.

I am working on a project which involves moving Jira onto the Azure boards. We use Azure DevOps for our repository and pipelines and we are looking to move on to Azure boards from JIRA for our ticketing or change request management.

Jira has helped our company because the board layouts are easier to use and has helped us see what is happening in regards to stories and bugs.

The layout, workflow, automation, and metrics are helpful in Jira.

The flexibility of defining your columns that can possibly contain multiple statuses is important. When you have teams that are different levels of granularity, the C levels, only care that it is in progress, but the leads want to know that it is in QA or development. You can accomplish these types of things with JIRA.

The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit.

When using the service desk and the developer, the transition could be better between the two. For example, we asked the support desk to send a ticket over to the development and it was a little bit cumbersome. We had to recreate another ticket for development, then we had two tickets, one service desk, and one development. It would be beneficial if the process was more smooth between those two packages.

I have been using Jira for approximately eight years.

The stability of the cloud version of JIRA is very good. However, we did have some issues with the on-premise version but the issue could have been because our servers were overloaded.

The scalability has been very good.

We have approximately 40 people using this solution in my organization, which is mostly everyone. It is used by many departments, such as project offices, development, and coding QA. The only department that is not involved in the use of the solution is the company support. I had worked at a company previously that used the JIRA service desk for their support and it worked well.

I have previously used DevOps and Rally.

JIRA installation is complicated. It is similar to a lot of other systems, the more flexible they tend to be more complicated they become.

We do the maintenance of the solution which is adding users and moving them around. The solution is very hands-off, it does not require a lot of maintenance.

We currently are evaluating other options and are doing a study to see if we are going to continue using JIRA or move to something else.

I would advise those wanting to implement this solution to contact an expert. 

This solution is a top-of-the-line CRM, I have used the others solutions, and it has the most flexibility and the best visibility.

I rate Jira a nine out of ten.

We use Jira for enterprise planning.

We like team collaboration and cross-functional collaboration.

The history with Jira is that it is a bit complex for many users.

There are too many features.

The user interface is complex.

I have been working with Jira for five years.

We are migrating to the latest version.

Jira is pretty stable.

It is scalable enough.

We have 1,000 users in our organization who are using Jira.

We plan to increase our usage.

Before Jira, we did not use any other solutions.

The initial setup is straightforward, nothing out of the norm.

We had a perpetual license but have changed to a subscription.

We are not satisfied with the pricing. It has become more expensive.

We would prefer it to be cheaper.

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

I would rate Jira an eight out of ten.

I primarily use the solution for project management. 

The product is quite easy to use and simple to navigate.

The solution isn't too difficult to learn.

It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage. You can really tailor-make your own dashboard depending on your needs.  

It's quick and very stable. 

I don't see many issues while I'm using it.

You can basically communicate with all kinds of different teams that are using Jira and you can do that under the product, as a single platform.

Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas.

Nowadays, you see a lot of product management tools, like monday.com and they are very user-friendly. They offer features that allow for cosmetic changes, and you can actually change the color and the form to your own liking. ira is lacking some of that flexibility. It's not critical, however, for the wider user base, many would like to see that.

I've been using the solution for three years. It's been a while. 

Overall, the performance of the tool is quite reliable with few bugs or glitches, and it runs very fast in the browser It doesn't crash or freeze.

The solution can handle a lot of tickets. I've seen it handle more than 10,000 with no problem. It's almost unlimited in terms of scalability.

I'm a customer and an end-user.

I'm using the latest version of the solution right now. I cannot speak to the exact version number we are on currently.

I'd rate the solution at a nine out of ten. We've been very happy with its capabilities. 

I would recommend the solution, as it is quite powerful.

We primarily use the solution for project management. 

What I like about this product is how you can manage from the project to the deployment, even using Bamboo or using Bitbucket. 

Being able to automatize the deployment of the solution has been great. 

We're not only managing documentation on the project task, but we're also handling the technical assets that are under the project. 

What I don't like is that perhaps there are not so many different apps that can add value over the management side of the product. They're not able to develop over Jira, even for normal technical activity signing. For managing the project better or for task documentation or even managing tickets or service needs in another way, there needs to be better customization or better apps.

I'm really obsessed with the idea of reducing the number of activities to have a general retail workplace. However, if we need to expand the use of the Atlassian suite to all the teams, all the people, we need something that can be, easier to use and has the ability to offer more guidance to those users that usually don't work with these type of tools. For example, ServiceNow doesn't fit all the needs in the company, however, it can be configured. You can develop so many different functions over it. I don't want to increase the payments and the number of licenses that I have to buy from ServiceNow. I would prefer to have my own developed team and try to define everything on our side - including the functionalities that I would like to build for those proposed functionalities.

I've used the solution in a structured way for about 18 months now. 

We have looked at and worked with several content-managed solutions in the last year. We're trying to build our retail workplace using ServiceNow, and, at the same time, increasing the use of the Atlassian suite. ServiceNow, we use for post activities such as service ticketing, service managing, and so on. 

The introduction of agile has moved us onto the Atlassian suite, which has been really very, very useful. At the same time, we have a partial solution that has been built over Salesforce, using the Salesforce development environment. 

Fortunately, we have so many different solutions for file management. We have FileNet, we have OneDrive. We have SAP. In terms of file management, we have so many different solutions, even Dropbox.

We are using the Jira service center and we are using Trello and Confluence as well.

The deployment is pretty straightforward. It's not overly difficult. We are able to automatize a lot of it. 

We're an Atlassian partner. 

In terms of project management, Trello is not enough of a solution to manage complex projects and maybe some new functions can be developed. I'm not saying that Jira has to develop that, or that Atlassian has to develop that. Perhaps there is something that we can do to create a referring community to develop those new use cases and more simple use cases, and, at the same time, use them for more general purposes in the company. Atlassian fits in the technical side, in the IT side really well. It just needs to move to become friendly in a retail workspace environment, outside of its traditionally technical background.

Overall, I would rate the solution at an eight out of ten.

I would recommend the solution to other users and organizations. 

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 primarily use the solution for software management. 

I really like the linking and user stories, and the formatting on the solution. The formatting options and linking the user stories have been great. 

You can export the whole backlog if you want to - including your roadmap.

The initial setup is easier than the TFS.

The UX and useability os good, especially if you compare it to a solution such as TFS.

You can use it right away without too much of a tutorial. 

The solution is stable. 

The scalability is good.

I would suggest Jira makes the format compatible with Microsoft Word. Currently, when you copy and paste something from Jira, such as tables, it won't be the same when you copy it into a Word file. There are formatting issues. 

If you have 70 or 100 stories, it doesn't work to copy and paste or export each one individually. There needs to be better configuration at a categorization level. 

There needs to be a way to export a user story. 

By default, Jira is epic and story only. It would be ideal if there was a different categorization between the two. It would be nice if there was a third story option. 

There should be a plugin for test cases. 

If the solution doesn't have third-party plugins for some features, they should add it into the main offering to make it more complete. 

I don't have a lot of experience. I only have about four months of experience or something like that. It's not a huge amount of experience, however, I got familiar with the basic features of Jira over that time. The first two months might have been on a trial version.

The solution is stable most of the time. Only rarely are there some points where it's not stable. For example, when you view some issues, sometimes it gives an error. Then, after that, if you refresh or you open it at another time, it may work again.

The solution can scale. If a company wants to expand it, it can do so.

We have more than ten people on the solution. 

If you need to find answers, the community FAQs are pretty good. I've found issues in there in the past that have helped me troubleshoot. So far, I'm pretty satisfied with that aspect of support.

The initial setup is straightforward and simple. It's not difficult or complex. 

I don't deal with pricing, billing, or licensing. I can't speak to the exact cost of the solution. 

We likely pay a licensing fee as we have more than ten people using the solution, however, I can't say what the exact cost is. 

I have been researching the difference between Jira and TFS, to decide what is better for our team to use. I'm very familiar with Jira. However, some of my team members have experience with TFS. I'm trying to decide which management tool we will use in an upcoming project.

I have found that, with TFS, a lot of the features are built-in, however, with Jira, you are required to add in plugins. 

I'm a customer and an end-user.

I would rate the solution at an eight out of ten. For the most part, we have been satisfied with its capabilities. 

I would recommend the solution, however, I would warn that likely a company will also need to add many plugins in order to get the solution to do what they need it to.

I primarily use the solution for use cases and make sure that our tasks and priorities are getting done.

I like that we can actually categorize the stuff from high priority to a lower priority. You can make categories and you can focus on the right items that need to be worked on. 

The initial setup isn't too complicated. 

The solution is stable. 

The scalability is good. 

It is not intuitive. It was hard for me to understand how to use it right away. It would be ideal if they could make the solution more user-friendly so that it is easier to pick up.

I haven't been using the solution for that long just yet. it's been about six months or so.

There are no bugs or glitches. It doesn't crash or freeze. it's reliable and the performance is good. 

The solution can scale well. it's pretty straightforward if you need to do so.

We have product owners, project managers, and scrum masters on the solution. I would say that we have a thousand people using it, however, I'm not saying that for sure, as the bank has 46,000 employees and I'm just a part of a small team. I'm estimating that I would expect over a thousand people to use it.

I have never used technical support. I've been able to manage everything and figure stuff out with the stuff I have here. Everything is available to me.

I did use a different solution, however, I switched when I switched roles at the company.

For the most part, the solution was set up for us. My understanding is that it was pretty simple I assisted a bit, and I found that the navigation piece was not enjoyable to implement. 

I'm not sure which version of the solution we're using currently. 

I'm a customer and an end-user.

I'd advise users considering the solution to make sure that they have a little time to review it and understand the tool and make sure they actually find that it is a good solution to meet their needs and that it's what they're looking for. From Agile delivery teams that are here to deliver their MVPs and stuff like that, I think it's great to keep track of all their backlogs and stuff like that. It is also great for someone from a use case perspective as they break it down well.

I'd rate the solution at an eight out of ten. Of course, I'm still learning it. That said, it's great for keeping track of all the items and the stuff that needs to be done and for the use cases that have been closed, to make sure that we get the proper sign-off and understand the line of business.