We performed a comparison between Jira and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Project Portfolio Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"Jira is very user friendly, easy to install, and easy to access."
"The solution has been very stable overall."
"Overall, the solution is very nice and has a variety of great features."
"The most valuable feature is the full integration between Work management, Source code management, and Test Automation."
"We integrate Jira with QRadar which is helpful."
"The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall."
"The monitoring, flexibility and tracking are really good in Jira."
"Whenever we have issues, there is always someone ready to help us. Their people are knowledgeable and responsive. They get to tickets quickly. Just three or four weeks ago, we were having issues with getting data into Planview. We submitted a ticket and the turnaround was probably 45 minutes to get a response."
"The data is the most valuable because the reporting that we provide out of Planview is priceless when compared to any other tool. The reporting has a variety of reports. It has the capabilities of Power BI. It gives us all these dashboards that we can show to our executive leadership, and they have been very well-received."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"The solution view into resource capacity and availability helps us to manage work."
"We're still in an early stage. Things will change as we use it more. I did program reports that are important and that will provide us with value."
"Our transparency is increasing a lot. It is helping us to get people together. There are no dark rooms anymore. In some areas or concepts, we want to add more light to every single concept. That's the big impact that the tool is having. It allows conversations between people."
"The sheer amount of information available in one single interface is valuable. Everything is there. It is also a lot of work to maintain all the information, but generally, you can find everything you need within this one tool."
"The following definitely need improvement: UI, speed, and mobile app functionality."
"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."
"I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice."
"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."
"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."
"Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches."
"Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"The technical people are very competent, but there is so much turnover in the people that we talk to, and that's frustrating. They will say, "We can make this work." Suddenly, that guy has left, and we have no one. Then, we have to start all over."
"When you think of planning at a PI level, roadmap planning, or release planning, I think they should make a little more headway into how agile delivery works, tying it back into the financials and the planning to Planview. I think it would be good."
"I would like to be able to copy and paste from Excel into work and assignments along with roles and hours, as opposed to having to type it out one by one."
"We have almost like a third-party group who has to do a lot of our configurations. It's a bit painful for us anytime we want to make a change. The other issue is that we have different groups all in the same instance. So, if one group wants to make a change, it impacts everyone. Then, we all have to come together, to say, "Yes, we approve this change, or no, we do not." Thus, it has not been as flexible for us."
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"There are some issues with how long it takes to load the data to Planview, It just depends on what your setup is. If there was a way Planview could maybe make the loading faster, in case you do have a lot of things going on with your setup."
"I think that the user interface needs some getting used to. It's not immediately intuitive. That's potentially room for improvement. I think also that an organization needs to have good support from some senior management to get something like Planview established."
"We had issues with the data rephrasing."
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 243 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. Jira is rated 8.0, while Planview Portfolios is rated 8.0. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Polarion ALM and Rally Software, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, SAP Portfolio and Project Management, LeanIX and JIRA Portfolio. See our Jira vs. Planview Portfolios report.
See our list of best Project Portfolio Management vendors and best Project Management Software vendors.
We monitor all Project Portfolio Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.