Khalid Qureshi - PeerSpot reviewer
Program Architect at Afiniti.com
Real User
Top 5Leaderboard
Lean focused project management tool that makes it easy to create and distribute workflows across different departments.
Pros and Cons
  • "This solution focuses on lean methodology which we have found useful and it can also be used on any device."
  • "Jira's collaboration and integration with other apps and tools could be improved."

What is most valuable?

This solution focuses on lean methodology which we have found useful and it can also be used on any device. 

In Jira Code, you can create workflows easily and distribute them within different departments. The user interface is easy to use. This is a simple solution for a new business that is not familiar with technology.

What needs improvement?

Jira's collaboration and integration with other apps and tools could be improved.

Jira does not focus on ITSM documentation and procedures. It is more advanced in user-friendly workflows but is missing the functionality of artificial intelligence AI which could be embedded in the ASM management.

For how long have I used the solution?

I have used this solution for six years.

What do I think about the stability of the solution?

We are using the on premises solution which is very stable. There is a team that is currently working on its performance tuning. This solution is suitable for mid-sized companies.

Buyer's Guide
Jira
March 2024
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the scalability of the solution?

Jira, compared to other market leaders like ServiceNow, provides a lot of features but focuses on service management only. I would rate it a three out of 5 for scalability. 

How are customer service and support?

We have not had any issues with Jira support. There is an online knowledge base and a growing online community which helps with troubleshooting. 

How was the initial setup?

The initial deployment was straightforward.

What about the implementation team?

We implemented this solution internally. 

What's my experience with pricing, setup cost, and licensing?

The licensing model for enterprise users is costly. We have more than 2000 users and it is becoming expensive to use.

What other advice do I have?

I would rate this solution an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Business developer at Bat.IT
Real User
Data functionality is easy to understand
Pros and Cons
  • "The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
  • "The features are not intuitive. It would be good if there were templates."

What is our primary use case?

Our organization is a software development company. We serve financial institutes that have between 8,000 and 13,000 employees.

We use Jira for process automation and as a workflow engine on the client's side. For example, a customer can fill out a form and ask a question, which is operated by Jira, and someone will be prompted to contact you with the answer. We created the forms designer and the roof engine and handle the process with the customer contact.

We are using Jira for automatic tools, so it is run on-premise.

What is most valuable?

The most valuable feature is that it has different APIs available, with good services, and it is completely by the books.

What needs improvement?

Jira could improve the documents management level. Our customers compare it to Office 365 and Sharepoint Online. They are focused on versioning of the document; Jira is missing this in their environment. It is missing functions for collaboration, like instant messaging. Currently, we try to connect the systems, we use Jira workflow which is connected to Office 365. 

Jira is trying to push for the online version, however, our customers are not ready to do that due to safety concerns.

The features are not intuitive. It would be good if there were templates.

For how long have I used the solution?

I have been using Jira for eight years.

What do I think about the stability of the solution?

Stability at the beginning had some troubles, but it is okay now. To maintain a large network, we divide it between operations and development. We have approximately six people involved.

What do I think about the scalability of the solution?

Jira is scalable.

How was the initial setup?

The initial setup depends on the project. Smaller projects where we are using minimal functionality can be quite simple. On the other hand, we have a monthly deployment process where we extend the solution, which is a complicated process because it's running a system with a lot of users.

What's my experience with pricing, setup cost, and licensing?

Pricing of licensing is too high.

What other advice do I have?

From a user perspective, Jira is simple to understand if they use its data functionality. If you want to extend it to custom feeds then you need further education.

If you are considering Jira, take a look at the online versioning and online pricing.

I would rate Jira an 8 out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Jira
March 2024
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
reviewer1740093 - PeerSpot reviewer
Works at a educational organization with 201-500 employees
Real User
Valuable links between tickets, good performance, but lacking integration
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Jira for approximately four years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not contacted support.

How was the initial setup?

The initial setup of Jira is straightforward.

What about the implementation team?

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

What was our ROI?

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

What other advice do I have?

I would recommend Jira to others.

I have not used many tools to compare Jira with.

I rate Jira a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Naresh Rayakwar - PeerSpot reviewer
Lead architect at Tech Mahindra Limited
Real User
Top 5Leaderboard
Useful for backlog management and sprint planning
Pros and Cons
  • "The two features that have been most valuable have been backlog management and sprint planning and tracking."
  • "This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning."

What is our primary use case?

The primary use cases for this solution are backlog management and sprint planning. Customers deploy this solution on-premises. 

What is most valuable?

The two features that have been most valuable have been backlog management and sprint planning and tracking. 

What needs improvement?

This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning. 

For how long have I used the solution?

I have been using Jira for almost three years now. 

What do I think about the stability of the solution?

This solution is stable. On-premises, the stability is okay, but when it's cloud-deployed, I think it will be more stable. 

What do I think about the scalability of the solution?

This solution is scalable, but I think it will be more scalable when we go with a cloud deployment. 

How are customer service and support?

I have never contacted support directly, but our team that takes care of maintenance, support, and customization connects with them. 

Which solution did I use previously and why did I switch?

I previously used Micro Focus ALM Quality Center for around five years. 

How was the initial setup?

Installation was done by someone else. For deployment and maintenance, we have a DevOps team of two or three. 

What about the implementation team?

I implemented through an in-house team. 

What's my experience with pricing, setup cost, and licensing?

We don't pay for licensing because we are using the Open Source version. 

What other advice do I have?

I rate this solution an eight out of ten. I think it's much better than other competitors' products. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Co-Practice Head, Digital Transformation - RPA Solution Architect at Royal Cyber Inc.
MSP
User friendly, stable, and scalable
Pros and Cons
  • "It's a Scrum tool, so it's very easy to use."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Manager, PMO at a educational organization with 1,001-5,000 employees
Real User
Intuitive dashboards with good visibility, stable, and easy to set up
Pros and Cons
  • "The dashboards are useful."
  • "For a non-technical person to use, Jira is not intuitive."

What is our primary use case?

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

What is most valuable?

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

The status of the different activities is also helpful 

What needs improvement?

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.

For how long have I used the solution?

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

We are using the latest version.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

The scalability can be complex if you are using workflows.

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

How are customer service and technical support?

I have not yet used Jira technical support.

Which solution did I use previously and why did I switch?

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

Along with Jira, we use Microsoft Azure DevOps.

How was the initial setup?

The initial setup is fairly straightforward. 

It was fairly simple for us.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Project Manager at a consultancy with 201-500 employees
Real User
Can customize entries and quickly update them
Pros and Cons
  • "A most valuable feature involves the ability to customize the entries and to update them quickly."
  • "Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people."

What is our primary use case?

We have been using Jira for schedule management as well as for making updates to our projects. I mention this in my capacity as a project manager. I most recently used the solution this year and did so for scheduled management of our varied tasks and projects. JIRA is actually used to put together an entire portfolio for each one of the teams, meaning for everybody. The solution listed each of our projects individually, with us needing to provide daily and regular updates. 

What is most valuable?

A most valuable feature involves the ability to customize the entries and to update them quickly. Unlike what was previously available, the solution allows us to create specific codes and symbols for the individual teams. The new version allows one to customize and to use demarcators. There is a code that can be entered in Align upon completion of a project or task and this apprises the project manager that it is time for its removal. 

What needs improvement?

Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people. However, I cannot state definitively if this situation owes itself to the way our team put the site together or to something administrative. When clicking the back button it would take the person to the wrong page, not to the one he desires. One would actually have no choice but to browse back to the portfolio and to find his group again and open it. Again, it is not clear to me if this problem lies with Jira or with the way our team laid out the site. 

What do I think about the stability of the solution?

I feel Jira is stable. The only hiccup which comes to mind is the one I mentioned, although it is not clear to me if this owed itself to the network we were using or to limitations of the application. Except for this, everything about the solution is stable. The only time a person can not look at the information is when the administrator announces his intention to remove it. 

What do I think about the scalability of the solution?

The scalability is pretty good and we started on this process from the moment we started utilizing the solution. While we had only three teams and three sections, between December and January 15th the developers came together and expanded from three to 76 different tasks across the different teams. By February there were over 300 teams. Expansion is easy and did not just encompass our teams but also provided links to others that were outside of our main team set so that there were reference points available.

How are customer service and technical support?

I would say the tech support is pretty good. I got back a couple of answers in response to an email I sent out. 

How was the initial setup?

It was quite easy for me to set up my own pages. I had a field day with creating my own test pages and was able to play around with them and simply test out the different settings. Pulling in new documentation was very easy. The same holds true with pulling in attachments and it was, consequently, easy to set up. As well, I was able to set up certain sub-pages for our team for going in and checking JIRA.

What about the implementation team?

There were initially eight people involved in the maintenance of the solution and deployment of updates. They had the people to whom they answered. We are talking about a large-scale effort. Without taking into account the Jira support line, I would say there were around 12 people managing and administering this version. For our specific team, there were around three. They were the actual decision makers. 

What's my experience with pricing, setup cost, and licensing?

I am not in a position to comment on licensing costs. 

What other advice do I have?

Our team does not use the solution exclusively. There are multiple ones which do, although I cannot state how many teams are doing so. I do know that the entire section of our agency is doing so and this accounts for a lot of people, well over a hundred. 

The solution is pretty good and is geared towards those with multiple teams who are using it for the same purposes as us. We use it for providing daily and scrub updates, for which it is really good, as it allows one to track every entry and see when it's entered, timestamp and all. So, if a person has a lot of mission-critical or time-sensitive activities, JIRA is pretty good for tracking and helping to keep everything organized.

While I am still biased towards services at the moment, I rate Jira as an eight out of ten, at it is really good and very functional. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Planning and Control Manager at a financial services firm with 1,001-5,000 employees
Real User
Provides flexibility to create different flows, responds to our needs in terms of scalability, and has good stability
Pros and Cons
  • "The flexibility to create different flows is most valuable."
  • "It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."

What is our primary use case?

We are basically using it to register all the requirements and issues so that we can track them and control the flow and different states. We also use it for reporting and configuring dashboards for portfolio management.

It is a SaaS solution, and we are using its latest version.

What is most valuable?

The flexibility to create different flows is most valuable.

What needs improvement?

It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios.

We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration.

For how long have I used the solution?

I have been using this solution for two years.

What do I think about the stability of the solution?

Its stability is very good. I have no complaints.

What do I think about the scalability of the solution?

It is scalable because it is a SaaS solution. It is the best choice for us because it responds to our needs all the time.

We have around 100 people in our organization who use this solution. They are developers, QAs, and managers.

How are customer service and technical support?

Their support was very good for some of our questions. We didn't have too many issues.

We also have a partner who helps us with all the contracts, payments, and other things. If there is an issue, we contact them, and they provide support.

How was the initial setup?

It was easy because the person who helped with portfolio management had previous experience with Jira. So, it was easy for us. It took about three weeks.

What other advice do I have?

The most important thing is to precisely decide your flows and different stages and cycles. If all these are very clear, you won't have a problem setting up Jira.

I would rate Jira a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.