JIRA Portfolio Reviews

As a user, my primary use case for JIRA Portfolio is mainly around project management, portfolio management, budget planning, and ideation. It is IT projects specifically related to the oil and gas domain.

The main feature of JIRA Portfolio that I find valuable is its alignment with the scaled agile framework. The portfolio planning, cross-program dependencies, and extensive reporting are very useful. The reporting feature is comprehensive and easy to use, which aids in planning and forecasting.

User experience should be more intuitive. Currently, it's not that intuitive. Additionally, a lot of querying and customization is needed for reporting. If there could be some templates out of the box, it would be helpful. Making the report creation process faster and easier with drag-and-drop features would be beneficial.

I have been working with JIRA Portfolio for around five years.

The stability of JIRA Portfolio is very good. In comparison to Planisware, it is very stable. I would rate the stability as nine out of ten since I haven't explored it thoroughly.

In terms of scalability, I would give JIRA Portfolio a ten out of ten. I did not see any challenges regarding scalability.

During our use of JIRA Portfolio, we had a dedicated account manager from Atlassian tech support. The support was good with no challenges, and I would rate it as a nine out of ten.

Positive

We are currently evaluating whether to continue with Planisware or JIRA Portfolio. In our current phase, we are using both, and we plan to make a decision by Q1 2025 on which solution to use long-term.

The initial setup was not difficult. I would rate the setup process as an eight out of ten. The organizational structure setup took about three weeks, and setting up the projects was pretty quick and easy.

Our internal team handled most of the deployment process, with consultants available for assistance as needed. We used consultants on an hourly basis to overcome challenges.

I am part of the delivery team and am not exposed to the commercial information. However, from what I understand, JIRA is competitively priced. It is not considered expensive in the market.

We are currently in the process of evaluating whether to use Planisware or JIRA Portfolio.

My advice to those considering using JIRA Portfolio is to go ahead with it. It is reliable and built with the realities of IT project management in mind. 

I would rate JIRA Portfolio a nine out of ten.

We are using all the tools of Google, but not as a collaboration. We are using JIRA Portfolio for making the process of authorization in this process, for change control, and for software delivery. We are using the JIRA Portfolio tool instead of SharePoint. We are using only Google.

JIRA Portfolio was implemented since 2021 or 2022. I have been dealing with JIRA Portfolio for maybe four or five years.

JIRA Portfolio is used for change management process, for authorization, and we use it for projects instead of Microsoft Project. We use JIRA Portfolio for the process of problem management and incident process through the service management of JIRA Portfolio.

We utilize JIRA Portfolio for projects and portfolio management.

All the business areas are comfortable with JIRA Portfolio. JIRA Portfolio has many features that we have not yet explored or utilized fully, but the power of JIRA Portfolio at this moment for the several areas in the business has been a very comfortable experience.

The cloud accessibility and quick task creation capabilities make collaborating with the tool a great feature for working with my team. Users can assign tasks to one or two people who can collaborate and document their work. That feature is amazing in terms of collaboration. While the tool does not currently support meetings, if JIRA Portfolio incorporates meeting functionality in the future, it would greatly enhance the process, especially for tasks requiring teams from different areas.

The setup process for JIRA Portfolio is complex.

JIRA Portfolio was implemented since 2021 or 2022. I have been dealing with JIRA Portfolio for maybe four or five years.

I do not have direct support for JIRA Portfolio as it is handled by another area, but I believe we have a provider for that. While it is not directly with the Atlassian company, I have heard that communication was easy. We are satisfied with the support from our provider.

Positive

There is significant return on investment as the benefits are numerous. The tool provides tracking for projects and activities, with detailed insights into which team members worked on activities and the time invested in each task. It is excellent for project observability, conducting projects correctly, and documenting incidents. These benefits provide good return on investment for the business.

I started using JIRA Portfolio for development. Typically, it was useful for backtracking in the first place and later for project planning. I tried to use it to track every kind of issue.

The most valuable feature of the product stems from the fact that it is able to give an oversight of what work is in progress while having a kanban board or similar visuals that can be used in an international context with video calls and where you can get away with just a piece of paper because you are not the same site. The good thing is that you don't lose the tickets, and you can connect them in different formats. You can connect the ticket if you want to track more static information on the wiki page, and such integration helps a lot, along with the other integrations with source code tools and other products.

From an improvement perspective, I would like to see the product of more integration capabilities with different platforms. The APIs work, but what my company noticed is that Atlassian offers extensions in the marketplace, and one also needs to buy new products it provides. The integration of the new products with the rest of the portfolio always takes some time, including for users to become familiar with Atlassian Assets and OpsGenie.

The product's performance is an area with certain shortcomings where improvements are required.

I have been using JIRA Portfolio for over a decade.

In terms of stability, if I consider the availability part, I can rate the product a nine out of ten. Our company rarely has seen an outage or an interruption in the tool's service. From the performance perspective, while on CloudFirst, it could sometimes be a little bit slower.

I haven't seen any issues with the tool's scalability.

Hundreds of people in my organization use the product. I don't have the exact license number, but for our business line, it must be a few hundred. Many people might not be using the same features offered by the product, but they all have access to wiki. For the main use case, my company has 40 users.

I have worked with other solutions in the past for backtracking and for software development. I can say that JIRA Portfolio is the best tool that I have worked with till now.

The product's initial setup phase is complex. If everybody fills in their time, then resource leveling can be done, but in an agile way of working, it's quite complex to make estimates and track time if you work on a lot of different items. You don't check the time on a minute-by-minute basis.

During the product's deployment phase, it helps that you can integrate JIRA Portfolio with your CI/CD pipeline to see planned work and tickets, along with pull requests or view code drops to see what the difference in the new releases of the tool and see what are all the code changes or changes in the planned work and it also allows you to have automatic release notes. When you have daily releases, you don't want to draft everything manually, but it is still relevant to have a quick view of how all the things are linked together.

I do not believe that the product provides value for money since I feel that it is quite expensive. I don't have a clear view of the cost associated with the licensing part of the tool. The product considers the license cost based on the actual usage of the product. My company has a premium license, and it is huge enough to be extended to everybody in my company, including the ones who have very limited usage of it. My company likes to have the product connected to the rest of the team, though many are not daily users of the solution.

Speaking about how the tool's road mapping or capacity planning features impacted our company's project management area, I would say that I haven't used it much. I think it could be useful to have some resource leveling across bigger teams, but I don't think it is currently used for such areas.

I think JIRA Portfolio is quite a complex tool with a lot of configuration options. You really need to have some people dedicated to seeing what is all in the box and what is needed for my business and gradually introduce them. Everyone can do something with Jira, but when you scale up, it can become messy so you need data architects and technical guys who can automate and glue the things properly to your business.

The product's integration capabilities work pretty well, especially considering that more tools are always needed in enterprise-sized businesses.

In terms of the value derived from the use of the product by our company, I can say that the integration of the tool's ticketing system with wiki and with software trackings, thereby giving a complete portfolio to users even though there are better or cheaper tools for individual things. You can have free wikis with the tool, but then they are not linked, which is good. I think the integration and also the fact that you have open APIs to connect it with other tools so that it is not a closed system. The product already has a big portfolio, but there are still many links that are valuable, and in the marketplace, it is a good tour considering all the extensions available in it from third-party products, though it may get complex to find the right solution. With some dedication, it is possible to find the right extensions for the product.

In general, I rate the product an eight out of ten.

We use Jira Portfolio in our organization for issue tracking and task management. We had many projects. We didn't use it much for forecasting, but we did use it a bit for release planning by assigning tasks to releases. We didn't use it for project management or scenario planning; we just used it for tasks.

The tool needs to improve its speed and response time. 

I have been working with the product since 2006. 

My company has 130000 users. 

I liked using the Jira Portfolio a lot. It was handy, easy to customize, and had many add-on options. Now we use Codebeamer, which can do the same things and maybe more. We're slowly phasing out the Jira Portfolio and not starting any new projects.

When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard they increased a lot, so we decided to stop using it.

I rate the overall solution an eight out of ten. 

The solution is simple to use. We use JIRA Portfolio with Azure Logic Apps, and it is easy to integrate them.

The solution should provide a monitoring interface for the customers to have more information about the issues. We cannot receive the information by mail. We can use the tool to share reports, but it should also have a space for customers to add comments. JIRA should provide more online video resources explaining how to use the solution.

I have been using JIRA Portfolio for one year.

I rate the solution’s stability an eight out of ten.

Overall, I rate the solution a seven out of ten.

Everyone mentions tasks using JIRA. It is used for various everyday tasks, including dashboards, sprints, backlogs, and workloads.

It has been very efficient for internal communication and managing different data and work projects. It tracks the progress, the development, and more. 

It is one of the important tools and one can easily maintain and manage the tasks in JIRA. 

The workflow and bucket features are most helpful. We never have code changes without a linked JIRA case. Code changes are linked to JIRA, and you can see the code changes within Jira.

 The roadmap in our capacity planning features impacted the project management. We're transitioning from Bitbucket to GitLab and JIRA, which are linked to GitLab. This change is necessary due to this transition.

The focus will be on commits. The focus will be on checking the message, confirming drastic data as a prefix. If not, then the commit will be rejected.

The products are getting bigger. So, learning JIRA is not so easy. There is a learning curve. 

It is not easy to understand all the workflows. 

I have been using it for seven years. 

I would rate the stability an eight out of ten. Sometimes, if you have a version change, even if you follow the process of "open," "in progress," "in review," "progress class," then "closed branch," and finally "close Jira," you might only change one line of code. But you still have to go through the internal process. It's modified coaching. It still goes over the entire process in ten minutes.

There are around 500 end users in the company. 

The customer service and support are good. 

We have a standalone team for the setup. 

It provides the most functions and is very agile, lean scrum. 

Overall, I would rate the solution an eight out of ten. 

I would recommend JIRA. It is based on Agile only. So if you want to learn JIRA, you first learn Agile office knowledge or cloud or function, something like this. Then you can understand JIRA too.

Originally, we used JIRA for help desk ticketing, but the biggest use case for the solution now tends to be supporting Kanban and scrum-based agile development.

JIRA Portfolio was a much more appropriate solution to support our move to agile systems development and implementation.

The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area. If you look at the videos they publish on YouTube, other platforms, and internally, they support their users pretty well.

The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve.

It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly.

Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.

I have been using JIRA for about three to four years.

The solution is pretty stable and the code is solid. I haven't dug under the covers of it particularly, but I do have some familiarity with these kinds of products and I get the sense that this solution is pretty well-designed and they've invested quite a bit in modernizing it and keeping it updated. It seems efficient. One of my latest implementations was using this solution with the Canadian government. They have a very extensive implementation of it and they haven't had any particular issues.

The solution is very scalable. I think it is probably more scalable than MS project server when it is used for project management. I've seen it used in IT shops with up to 8,000 people, so it's pretty scalable.

Prior to using JIRA we were much more focused on waterfall development and used MS Project Server.

I'm not very familiar with the setup on-prem. My company is a consulting firm and the clients that I have worked with personally were running the solution on-prem, so they had their own technology people setting it up. I think it's a fairly straightforward thing to manage and set up. These days, Atlassian is focusing much more on their cloud version of the solution, which is probably the most straightforward way for a new user to adopt the product.

I can give you some general advice about setup cost, pricing and/or licensing. Here are some points to consider:

• 
  JIRA Portfolio is now called Advanced Roadmaps and is available in Jira Software Cloud Premium¹². The pricing for this plan is $10 per user per month for up to 10 users, and $7 per user per month for 11 to 100 users¹. This plan includes unlimited storage, advanced permissions, project archiving, data residency, and more¹.


• 
  If you want to use JIRA Portfolio as a self-hosted solution, you can still purchase Portfolio for Jira Server or Portfolio for Jira Data Center². The pricing for these options depends on the number of users and the type of deployment. For example, for up to 10 users, the Server license costs $10 (one-time payment), while the Data Center license costs $1,100 per year².


• 
  JIRA Portfolio is also compatible with Jira Software Cloud Standard and Jira Software Cloud Free², but with some limitations. For example, the Standard plan has a 250 GB file storage limit, while the Free plan has a 2 GB file storage limit and a 10 user limit¹. The pricing for the Standard plan is $7 per user per month for up to 10 users, and $5 per user per month for 11 to 100 users¹. The Free plan is free for up to 10 users¹.


• JIRA Portfolio is not a standalone product, but an add-on for Jira Software. Therefore, you need to have a valid Jira Software license or subscription to use JIRA Portfolio³⁴⁵. You can also integrate JIRA Portfolio with other Atlassian products, such as Confluence, Bitbucket, and Trello³⁴⁵.


• 
  JIRA Portfolio offers a free trial for both Cloud and self-hosted solutions, so you can test it out before you buy it²³⁴⁵. You can also request a quote from Atlassian or a partner to get a customized pricing estimate²³⁴⁵.

I hope this gives you some idea of the setup cost, pricing and/or licensing of JIRA Portfolio. If you have any specific questions, you can contact Atlassian Support or visit their [Help Center]. 😊

: https://support.atlassian.com/...

I did not choose JIRA Portfolio myself, as it was already implemented in my organization when I joined. However, there are some other options that are similar to JIRA Portfolio in terms of project management and road mapping. Some of the most popular JIRA alternatives are:

• 
  ClickUp: A cloud-based project management tool that offers flexibility and customization. It supports agile methodologies, time tracking, reporting, and integration with various tools. It also has a user-friendly interface and a free plan for up to 100 MB of storage¹.


• 
  Basecamp: A web-based project management and collaboration tool that helps teams stay organized and communicate effectively. It features to-do lists, message boards, schedules, documents, and chat. It has a flat pricing of $99 per month for unlimited users and projectsBasecamp" rel="nofollow noopener">².


• 
  Wrike: A cloud-based project management and collaboration tool that helps teams manage complex projects and workflows. It features Gantt charts, Kanban boards, dashboards, reports, and integrations. It has a free plan for up to 5 users and paid plans starting from $9.80 per user per monthWrike" rel="nofollow noopener">³.


• 
  GanttProject: An open source desktop project management tool that focuses on creating and managing Gantt charts. It allows users to create tasks, assign resources, set dependencies, and track progress. It is free to download and use⁴.


• 
  Gantter: A cloud-based project management tool that integrates with Google Drive and Google Apps. It allows users to create and edit Gantt charts, collaborate with team members, and manage risks and issues. It has a free plan for up to 50 projects and paid plans starting from $5 per user per month.

Of course, there may be other tools that suit your needs better. You can always do more research or try out different tools before making a decision. 😊

My advice would be to carefully consider your rollout strategy, the amount of training involved, your communication, and organizational change around the use of the product. Think carefully about how you're going to use it. It's pretty malleable in that you can use it in a lot of different ways, so think that through. I suspect that Atlassian provides support in that area, but whether they do or they don't, it's something you're going to have to put some work into for a successful implementation.

Also, as far as a maintenance team goes, there's a couple of layers to consider. The people needed for looking after the system admin on the product would be very low. I think two or three people would be enough backup to make sure that you have continuity. There's also another layer of admin that is more involved in some of the setup and customization of the product for different use cases. I think you would need more people, maybe like five to ten, on that tier of supporting the users. You need that kind of support because the product is a little too technical to hand it to a project manager. Unless they're pretty well-versed in it, they are going to need some support for setup and usage in their particular application of the product.

I would rate this solution as a nine out of ten.

The primary use case is project management. 

The entire features that are required for managing the product's communication between the team there are valuable. Managing product development and managing inter-team communications are also valuable features.

Maybe integration with other tools could be made easier. 

I have been using this solution for three years.

I would rate the stability a nine out of ten. There was no downtime, no issues.

It is a scalable solution that's suited to our requirements for small teams. I'm not sure about larger teams. So, it's limited to whatever users it has. So that's suited to our requirements.

I would rate the scalability an eight out of ten, as far as my experience goes with the tool, but I haven't used it on a larger scale.

I never needed any support. I'm a primary or maybe average user, so nothing extensively that I've used. So I have never needed any support.

It was absolutely easy to set up and work with Jira, so that was absolutely easy.

Jira is a SaaS solution, so there is nothing to be deployed. It's an on-cloud solution.

Currently, I use the free version for personal use.

I find it simple compared to Azure DevOps. Comparing both Azure DevOps and Jira, then Jira is simpler compared to DevOps.

Overall, I would rate the solution an eight out of ten. It is a good tool and easy to use. It is very easy to start using the tool. It is very easy to understand and use the tool.

Our organization uses the solution in scrum meetings and cycles for the internal teams. JIRA Portfolio is also used for tracking stories, and roadmap planning. In our company, I am also working on JIRA administration to configure the entire cycle of the stories and Epics by adding customized fields and workflows.

I have used JIRA Portfolio to adjust and add flexibility to the workflows according to the team's input in our organization regarding their working process. 

The backlog view feature is highly valuable and helps manage stories. JIRA Portfolio assists in prioritizing which stories the team in our organization should work in sprint and which ones can be postponed. The sizing of each story and planning the ideal size for each sprint is also carried out using JIRA Portfolio. 

The reports generated using JIRA Portfolio are not intuitive enough. The product should also provide report customization capabilities. For instance, if I need to create a chart on the dashboard , I can only generate the chart in tabular format using the filters and widgets offered by JIRA.

Thus, the solution should allow chart generation in the form of a histogram or other chart formats. The product presently lacks visualization capabilities for reporting. In future releases of JIRA Portfolio, the workflow, including the templates and forms, needs to be further simplified; the vendor has already made simplifying efforts in past releases. There should be a portfolio or workflows for startups adopting JIRA Portfolio. 

I have been using JIRA Portfolio for eight years. 

I don't recall any instances where I have faced difficulty in accessing the solution. I would rate the stability a ten out of ten. 

I would rate the scalability a ten out of ten. 

Previously, in our company, Asana was being used, but as it's a project management tool that operates through resource utilization, it wasn't suitable for our use cases, and thus, we shifted to JIRA Portfolio. 

I would rate the initial setup an eight out of ten. Before adopting JIRA Portfolio, when I was comparing multiple products, including pricing and other differences, I found the setup process was not as simple as I expected, and it was time-consuming to find some specific information regarding the setup. 

The deployment process involved creating an account and inviting the rest of the organization's team and few integrations were needed. At the beginning of creating an account with JIRA Portfolio I had to create a migration project between Asana and Jira because our organization was working with Asana before using JIRA Portfolio. The deployment of JIRA Portfolio in our organization took just a day. 

In our organization there are ten users of JIRA Portfolio as we are using the free edition. But our company has plans to increase the usage in the future. 

The price is reasonable for the time being as our company is in the early phases and we need to cut costs as much as possible. Our company is presently relying on the free version of JIRA Portfolio, but the price of the complete version is also quite reasonable. 

I used Microsoft TFS a long time ago, and then I have also evaluated and worked on Asana. Our organization was using Asana six months ago and we realized that JIRA Portfolio is a better solution for managing the backlog and working on trial methodologies or scrums. 

The solution interface allows the view of name boards, lists, calendars, and timelines for the projects. The timeline view is highly beneficial for checking the stories dependencies on the timeline. Certain customizations can also be implemented in the timeline and the view can be changed between monthly, quarterly, and yearly. The timeline feature also provides a holistic view of all the stories in the backlog, including the completion time required for each story.  

JIRA Portfolio is easy to integrate with other tools. In my organization, I use JIRA Portfolio in integration with Slack, this is advantageous because it allows me to track whenever a team member adds a story or task. The aforementioned integration additionally allows me to monitor which project or tasks each member is engaged and I can make adjustments accordingly to the stories activities if needed.

For instance, when I check through a notification that a team member is working on a story that is not yet ready to work, I communicate it to the team member to refrain from working on that specific story. In our organization, JIRA Portfolio is also integrated with Outlook. 

The solution has allowed seamless communication between our company's managers and the rest of the teams, providing a holistic view of workflows and assisting in organizing the whole product cycle. Overall, I would rate JIRA Portfolio an eight out of ten. 

We use the tool to track issues and develop pipelines. We also use it for versatile projects in the IT department. It helps to track KPIs, present progress to the business with dashboards, and complete the QA team's plans.

What I like about the product is its extensive features, particularly the wide set of attributes for tracking issues. Jira Portfolio allows us to track not only the overall project but also specific components within it. This is beneficial for all stakeholders, including developers and business owners. For example, business stakeholders can track all issues, regardless of status. 

When using a scrum board, it only shows the current or open sprint. However, we also need to see past and future sprints, which is important for planning the next sprint. To solve this, we tried using a Kanban board instead, but since we follow the Scrum methodology, it's not the ideal solution.

I have been using the product for one and a half years. 

I haven't encountered any system issues myself. During my time with the company, we've had at least one upgrade of Jira Portfolio. 

My company has around 30-50 users for Jira Portfolio. We have around 100 licenses. 

The solution's support is good. 

We know about Jira Portfolio's work and capacity planning features. However, we do not use them. Instead, we use KPIs relevant to our business. I rate the overall solution as nine out of ten. 

I would recommend the product for IT project teams because of its stability and wide range of functionalities. Although we don't use the capacity plan feature, I recommend it. It's very useful for various purposes. 

We have integrated the tool with Lucidchart and Power BI. It has add-on functionality.