JIRA Portfolio Review

A user-friendly solution that adapts to the customer's needs, but flexible add-on pricing is needed

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.
More JIRA Portfolio reviews from users
Learn what your peers think about JIRA Portfolio. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
521,637 professionals have used our research since 2012.
Add a Comment
ITCS user