Try our new research platform with insights from 80,000+ expert users
it_user1106190 - PeerSpot reviewer
Co-Founder at up2metric P.C.
Real User
Our processes are more efficient and easier to be tracked which enables work to be more organized
Pros and Cons
  • "The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
  • "I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."

What is our primary use case?

Our primary use case of this solution is for organizing our projects and as a tracking solution for our software projects.

How has it helped my organization?

Before JIRA, we used to organize our software with Bitbucket but now, with JIRA, it is more efficient to organize all the work in the timeline, make long-term plans for one or two months, know what our deadlines are, and write short summaries in the backlog. The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized. 

What is most valuable?

We use all of the features. The most valuable features are the reporting of the speed of the team's progress and the long-term organization of our projects in the timeline. 

What needs improvement?

I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear. Now we are using next-generation projects, so it's simpler to set the projects up than it was in the past. There is some work to be done there to have a clearer interface and workflow of how to organize a simple software project.

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.

For how long have I used the solution?

I have been using JIRA Portfolio ( /products/jira-portfolio-reviews ) for six months.

What do I think about the scalability of the solution?

We have nine users using this solution. We do have plans to increase the usage. Gradually, all of the people on our team will use it and even more when a new developer or new employee comes to the company. We spend time getting familiar with JIRA then we organize the work to be done in the day in JIRA.

How are customer service and support?

I only needed technical support once. We got a very specific and straightforward answer. From that experience they were good and very efficient.

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

We were previously using Atlassian Bitbucket. Bitbucket is only good for tracking down issues but it is not helpful to organize everything and see how fast you are proceeding. With JIRA, there are a lot more features actually managing a project.

How was the initial setup?

The initial setup was straightforward. 

What was our ROI?


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

We have nine people using it so we have a standard cost of approximately $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher.

What other advice do I have?

I would definitely suggest going for it.

I would rate JIRA Portfolio an eight out of ten. To make it a perfect ten it should have a better user interface, be more clear, and more responsive.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Agile Coach at a tech services company with 201-500 employees
Real User
Good graphics and charts but we need a custom and limited dashboard for our customers to use
Pros and Cons
  • "The graphics and the resolution of the work are very good."
  • "If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out."

What is our primary use case?

We are in a very large company and I am an Agile Coach in our department.

What is most valuable?

All of the charts, including the Burndown chart, are very useful for us.

The graphics and the resolution of the work are very good.

The JIRA command line is also a very valuable feature.

What needs improvement?

We would like to have an option for a secure board that we can give to our clients that would allow them to see certain aspects during development, but not so much that they can steal all of our information. A dashboard specifically for customers would improve this solution.

Sometimes I have a customer-solution in addition to the more general solution. I would like to be able to differentiate these using perhaps a different color.

If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out.

It is hard to work from the bottom up. If you tap on your epic you can see its features, and if you open its features you can see user stores. If you go on, if you are going from top to bottom, it works well. However, if you want to go from the bottom up, it is very hard to do.

For how long have I used the solution?

I have been using this solution for six months.

What do I think about the stability of the solution?

The stability of this solution is good enough.

What do I think about the scalability of the solution?

The scalability is ok and we have had no problem with it.

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

We have used JIRA in this company for many years but we just recently started in this department. In this department, we used to use another solution.

What other advice do I have?

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