Try our new research platform with insights from 80,000+ expert users
reviewer1398831 - PeerSpot reviewer
Software Developer at a manufacturing company with 5,001-10,000 employees
Real User
Handled SDLC from end-to-end and fits well into an Agile environment
Pros and Cons
  • "The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects."
  • "Converting a task into an epic is very troublesome."

What is our primary use case?

I am a software developer and we use this product for end-to-end SDLC. It begins with the requirements gathering, then continues with tracking features and planning our sprints. We also use it for tracking bugs.

What is most valuable?

The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects. For example, if you create a new ticket, issue, or feature, then you classify it accordingly and you can assign it to an ongoing sprint.

You can look at the sprint backlog to see what features are planned, how many are in progress, and how many have been completed. This helps during reviews because you can get information about the velocity of the team. If somebody should leave the team for a while, or are otherwise unavailable for work, then the velocity calculations are readjusted.

What needs improvement?

Converting a task into an epic is very troublesome. As it is now, if you make the mistake of creating the wrong thing then you just have to delete it and start again. If you could convert between things such as features and tasks then it would be helpful.

For how long have I used the solution?

I have been using the Jira Portfolio for about four years.

Buyer's Guide
JIRA Portfolio
December 2024
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
832,138 professionals have used our research since 2012.

What do I think about the stability of the solution?

We use Jira on a daily basis and I cannot recall having any issues with stability.

What do I think about the scalability of the solution?

It is easy to scale but of course, the problem is that it needs licenses. As the licenses fit into a plan, it can be kind of tricky. When you want to procure additional licenses, it is a long path.

For example, if you have licenses for 50 users and you see that you need a license for another 10, then you can't just purchase a small number. At a certain point, you have to move up to 500 users, which is quite a jump.

Currently, we have about 60 users.

How are customer service and support?

I have not been in contact with their technical support team, although I do go through the community forums. I get details on new features that are going to be released and other such information, but I have not had to contact support for any specific issue.

How was the initial setup?

The initial setup is pretty straightforward. Somebody who knows Agile well will have no difficulty with Jira. On the other hand, somebody new to Agile may face some problems in the beginning. 

What about the implementation team?

We do not have any dedicated staff for maintenance. For the operation of it, we do have a facilitator and a scrum master who manages things for each project. However, maintenance is very straightforward. We don't need a full-time administrator working on it. A couple of people working part-time can take care of it.

Internally, people within a project may need some help when it comes to things like planning. In this case, they will get help from the scrum master.

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

We pay our fees annually, although monthly payments are also available.

What other advice do I have?

From a developer's perspective, this tool works fine and I don't have any complaints other than wanting to convert between features, tasks, etc, when a mistake has been made in creating one.

The only advice that I have for people who are implementing Jira Portfolio is to make sure that they manage their licenses properly.

I would rate this solution a nine 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
Owner at YggVal
Real User
A user-friendly solution that adapts to the customer's needs, but flexible add-on pricing is needed
Pros and Cons
  • "With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things."
  • "This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."

What is our primary use case?

The primary use case for this solution is to manage the work that has to be done, everything else is on a repository that is maintained by another tool.

It's how the work has been designed at the beginning of the project. We have one repository where we store all of the requirements, the testing, and all of the activity trackings are done in JIRA.

The deployment model was on-premises.

How has it helped my organization?

There hasn't been an improvement because we were using JIRA solutions before.

What is most valuable?

It is difficult to narrow it down to features. It's one solution as a whole and to point out certain features is complicated.

What needs improvement?

There could be many things that could be improved but we haven't been working with it long enough to accurately find the weak points.

The pricing of add-ons could be improved. You should have the option to pay only for the users concerned, that would be fine, because of the dashboards everybody has access to the dashboard.

This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

This solution is stable.

What do I think about the scalability of the solution?

This solution is scalable.

How are customer service and technical support?

I have not had any experience with customer service or technical support.

Our IT department handles this area.

How was the initial setup?

Our IT department completed the initial setup, so I am not sure how complex it was.

What about the implementation team?

The implementation was done through our IT department.

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

The pricing of the solution is expensive. 

When you install any add-on, you have to pay for each and everyone who is declared on the system in order to have the add-on working. If you have anywhere from one hundred to five hundred users and even if you only have two hundred users using this solution, you have to pay for them all.

Which other solutions did I evaluate?

We evaluated other options but JIRA was already in place, which is one of the reasons we stayed with JIRA.

What other advice do I have?

We are dealing with several products and clients, and each product has it's good points and it's weak points.

I don't have an opinion because I think that a good process does the job and you can apply a good process to any tool. 

The tools are more and more user-friendly. Even JIRA.  

When you want to implement something, keep it simple and it will work.

With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things.  

In the end, it needs to fit the process. If the process is of poor quality, then your tool will look poor.

For the most part, with several tools, you can do nearly anything.

JIRA is a good tool. Perhaps a little bit too much to configure and adapt, because it can be adapted to any kind of customer's needs and it's not dedicated to a specific solution, but it does the job.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
JIRA Portfolio
December 2024
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
832,138 professionals have used our research since 2012.
reviewer1158522 - PeerSpot reviewer
System Engineer at a computer software company with 10,001+ employees
MSP
Useful dashboard, beneficial portfolio view, and feature rich
Pros and Cons
  • "The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good."
  • "The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."

What is our primary use case?

We use JIRA Portfolio for management. It handles all our stories and we use the dashboards and reports. We are not fully utilizing all the features, and we use Tableau on top of it for our portfolio-level dashboards.

What is most valuable?

The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good.

What needs improvement?

The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise.

JIRA Portfolio should work on an intuitive way of querying and having different views, which will help us to track the progress. When things have been visualized they are more easily understood.

For how long have I used the solution?

I have been using JIRA Portfolio for approximately one year.

How are customer service and support?

I have not contacted technical support, but my installation or administrator team has contacted them.

What other advice do I have?

I would recommend that those wanting to implement JIRA Portfolio do a smaller implementation first. Once they know the features then they can do a full-scale customized implementation for exactly what they need with the appropriate features. 

I rate JIRA Portfolio an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Works at a tech services company with 1,001-5,000 employees
Real User
A powerful tool which is very reliable and stable
Pros and Cons
  • "The status update function is the most valuable feature."
  • "The data query language needs improvement."

What is our primary use case?

I'm a product manager, so I create entries covered for two products that are developed by the engineering team.

What is most valuable?

The status update function is the most valuable feature. 

What needs improvement?

The data query language needs improvement. 

For how long have I used the solution?

I have been using JIRA Portfolio for ten years. 

What do I think about the stability of the solution?

Jira is a highly stable solution. I would rate the stability a nine out of ten. 

What do I think about the scalability of the solution?

One thousand users are using the solution at present. 

How was the initial setup?

The initial setup is straightforward. The integration with Slack is very good. 

What other advice do I have?

Jira Portfolio is a powerful tool which is very reliable and stable. I highly recommend the solution. Overall, I would rate the solution a nine out of ten. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Test Manager at a financial services firm with 11-50 employees
Real User
Has a good dashboard and is user-friendly but the setup needs improvement
Pros and Cons
  • "The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
  • "The initial setup could use improvement."

What is our primary use case?

Currently, we use the on-premises deployment model but we are moving to the cloud. Amazon is part of it but we are in the evaluation part. Our primary use case is for workflow and regression testing. 

What is most valuable?

The dashboard is the most valuable feature. The user experience is very good, it's easy to use.

What needs improvement?

The stakeholders have to decide to use JIRA and that's the problem. Not all the stakeholders are in touch with JIRA but we need their budget for the whole team to get the opportunity to use JIRA. It's not a problem with the tool, it's our organization. Some of the stakeholders have other opinions and they like to use other tools.

The initial setup could use improvement. 

For how long have I used the solution?

I have been using JIRA Portfolio for eleven years in total.

What do I think about the stability of the solution?

Stability is very good. It's an easy to use and nice tool. We wanted to and we have bought licenses. For the bank, we have 250 users at the moment. We will increase it up to 500 users.

For maintenance, at the moment we just have a crew that takes part in the maintenance. It's only one or two people. 

How are customer service and technical support?

We don't contact their technical support very often. Most of the things we do by ourselves, and we look for some videos on YouTube for such things. We are in a group and there we get some information about JIRA. For most things we need, we get our own information.

How was the initial setup?

The initial setup was complex. We have Agile teams and we have classic teams and the waterfall development. We have to integrate both and we have to create a workflow that can be used for all of these aspects. Our governance in Germany for a bank is difficult. We have many things to keep in mind.

The deployment only takes two weeks but the difficulty is that we have many systems. Our old system is divided into 10 subsystems, so when we deploy we have to use other things. We must look for every single system. We'd like to integrate with JIRA but at the moment it's not in our book.

What other advice do I have?

I would rate it a seven out of ten. I don't know everything about the solution and every feature. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
PankajKumar12 - PeerSpot reviewer
Data Engineer at a media company with 10,001+ employees
Real User
Reliable with great features and helpful technical support
Pros and Cons
  • "The initial setup is simple."
  • "If you want to generate a report for individual usage, it's difficult."

What is most valuable?

The initial setup is simple. 

It is very scalable.

The product offers good stability.

Jira has many features that companies can explore to see which ones are best for them and their internal needs. 

Technical support has been good so far.

What needs improvement?

I haven't seen many drawbacks on the Jira side. 

If you want to generate a report for individual usage, it's difficult. The reporting can be improved.

For how long have I used the solution?

I've been using the solution for almost two years. 

What do I think about the stability of the solution?

Its stability is great. We don't deal with bugs or glitches and it doesn't crash or freeze.

What do I think about the scalability of the solution?

The product can scale if you need it to as a company.

How are customer service and support?

We are satisfied with the technical support. Overall, I find them to be quite helpful. They are good.

How was the initial setup?

The implementation is straightforward and simple. It's not difficult at all.

If you have a cloud-based solution, you only require four or five staff members to maintain the product.

What about the implementation team?

We had the assistance of an integrator when we set up the solution initially.

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

We pay a yearly licensing fee. Everything is included in that price. There aren't extra add-on fees to take into consideration. 

What other advice do I have?

We are a customer and an end-user.

I'm using the latest version of the solution. 

I would recommend the product. Companies can use it without having to worry about any hiccups. 

I'd rate the product as a seven out of ten.

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
Principal Technical Lead at Tieto Sweden AB
Real User
Provides a lot of plugins but it's not so user-friendly
Pros and Cons
  • "The customized workflows we can define are very valuable. JIRA's private projects is very useful as well. There are also a lot of plugins that they provide."
  • "I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."

What is our primary use case?

We use JIRA for project management.

How has it helped my organization?

We were able to implement the Kanban and Scrum methods using JIRA. That was a really good argument. We had been using the waterfall method, so this really helped us to get that out there to our general way of working.

What is most valuable?

The customized workflows we can define are very valuable. JIRA's private projects are very useful as well. There are also a lot of plugins that they provide.

What needs improvement?

I think their view needs to be more user-friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using.

There are many issues, but I would say the UI needs to be improved most. Also, some training documents need to be there with respect to their configuration. They don't have training documents easily available. You really need to figure it out by yourself. That is something they must improve.

For how long have I used the solution?

We've been using this solution for six years.

What do I think about the stability of the solution?

It's quite stable. We have not had any problems.

What do I think about the scalability of the solution?

It's scalable. We currently have 45 users, with six dev users and two people for maintenance. 

We will keep on using it. Whether we expand our use depends on our entire portfolio and the product growth that we are catering to our customers.

How are customer service and technical support?

It's not that good. I would give it a rating of three out of five, on the basis of price. They need to add improvements because it is not as easy to reach out to these people as necessary. I would expect them to have a call center or something, but they don't have one. We have to write down our messages and send them to support. It is not easy to solve our issues.

How was the initial setup?

It was definitely complex to set up. It was difficult right from the start, by applying the project setting configurations. Popping up the custom fields and relating it to the workflows was also difficult. Identifying a security policy on top of that and adding the group was really complex, too.

Deployment took almost one month's time to set it up and get started.

What other advice do I have?

I would rate this solution as seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Functional Analyst at a computer software company with 201-500 employees
Real User
It's easy to manage, create tickets, and change the status of delivery reports.
Pros and Cons
  • "Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
  • "The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client."

What is most valuable?

Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated.

What needs improvement?

We sometimes have issues importing and exporting Spanish data because we use accents, and they don't always export correctly.  

The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client. 

For how long have I used the solution?

We've been using Jira Portfolio for one year.

What do I think about the scalability of the solution?

Jira Portfolio is highly scalable. You can manage user connectivity and add more licenses within the tool. It's very simple and easy. We have no plans to increase usage, but the company can add more users if needed.

How are customer service and support?

All our issues were solved, and Atlassian support was excellent.

How was the initial setup?

Setting up Jira is simple for the user. The initial implementation takes about one week, and the sandbox can be deployed in less than a month. I handled it all myself, but there are 10 people on our IT team.

What other advice do I have?

I rate Jira Portfolio nine out of 10. 

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