We performed a comparison between JIRA Portfolio and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The initial setup is simple."
"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."
"In general, the valuable features of the tool are its capabilities concerning dependency reports and task status."
"Jira's Structure, agile, and Kanban boards are helpful. I also like JQuery, which allows you to fetch the relevant set of data. We use JQuery, JQL, and the Structure board a lot. Kanban boards help us monitor daily tasks, and we review the progress using the burndown charts."
"The feature that we like the most is that JIRA enables modules. Atlassian provides a lot of products around JIRA, such as compliance for the documentation, BitBucket for the Git version. We are new to these products developed by Atlassian, but they can integrate very easily. Generally, when an editor is developing a solution, they think about integrating with JIRA. When we are looking for any other solution, they plan to easily integrate with JIRA."
"The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it."
"The integration is very good. We've more or less integrated with everything including reporting and registering."
"I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely."
"The portfolio and technology management are well built."
"The most valuable feature of this solution is reporting."
"A lot of of the value is around the project metrics so far but as I get more plugged into the strategic management, it's strategic planning and programs and then tying that into outcomes. I work with executive leadership and that's really what they're looking for, to say, "Okay, what outcomes do we want to achieve and how are we going to get there, plan that out, sequence that out, and then get the work to do that? And then track the work back to where we're headed with our outcomes.""
"We have a fairly good picture of time tracking."
"It maps back to our SDLC process pretty well. I'm able to see the stage of where things are at. We also use Azure DevOps for all of our requirements and our coding."
"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."
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool."
"It gives us the vast ability to churn out-of-the-box reports and have an overview about approach rates and resource utilization."
"Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support."
"Requires some effort to insert functionalities and that could be simplified."
"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."
"We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa."
"The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA."
"The initial setup could use improvement."
"The integration needs to be done with different tools."
"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."
"We don't use the Progression feature. We will use it at some point in time. Until then, we want to have a way to set time to help decide what's in the past, present, and future. It is one of the things we've been discussing with Planview."
"I would like a bit more flexibility, as far as the configuration, and have additional capabilities to configure, making it more flexible for our use."
"Support is still a challenge. We find it challenging more due to the responsiveness and getting a case or ticket assigned to an analyst. That's what I was just doing. I was following up on an email that we opened last week. We haven't heard anything, so following up on that."
"The only area that I can see currently needing improvement is just the modernization of the look and feel of it."
"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."
"Its ability to create summary reports across multiple projects is very limited. In terms of the out-of-the-box reporting for summary reports, the reporting that we typically leverage is around forecasting for resources, timesheets, and actuals, and just looking at what is the capacity. There is no real summary of what work is being done and how work is being accomplished. So, what we typically do is that we get a copy of the data files from Enterprise One daily, and then we have a team that manages the data mod outside of Enterprise One. They use data from Enterprise One as well as other additional sources to provide the reporting that we share with the management. So, we leverage a lot of Enterprise One data for reporting, but we don't use the reporting capabilities within Enterprise One. So, reporting can be improved, and they could help us make more customized reporting. I know it is very configurable out of the box, but we have to leverage an outside data mod that pulls in a lot of data from Enterprise One. So, the reporting function, and being able to customize reports, is the area that could be very beneficial."
"I would like to see more documentation pieces. Right now, they do have the content repository. I would like to see more out-of-the-box features with document repository capabilities."
"I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 46 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. JIRA Portfolio is rated 8.0, while Planview Portfolios is rated 8.0. The top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". 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 Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Project, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, SAP Portfolio and Project Management and Jira. See our JIRA Portfolio vs. Planview Portfolios report.
We monitor all Enterprise Agile Planning Tools 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.
