Currently, portfolio rollups only support numeric custom fields, which limits visibility at the portfolio level for non-numeric data. As a Product Manager, I’d love to see the ability to roll up single-select custom fields — particularly those tied to custom task types — into the portfolio view.
My specific use case:
I have tasks using a custom task type that are multihomed across a main project and a quality testing project. Each task has a project-level single-select field with values like Pass or Fail. Right now, there’s no way to surface an aggregated view of those Pass/Fail values at the portfolio level — meaning I have to manually check each project to understand overall quality testing outcomes.
Being able to roll up these values into the portfolio view (e.g. as a count of Pass vs. Fail across all projects) would give portfolio managers instant visibility into quality status without leaving the portfolio.
This would be especially powerful for teams running stage gate processes, where go/no-go decisions depend on quality outcomes across multiple projects.
Would love to know if others are facing the same limitation, or if there are any workarounds!?
Hi @Rebecca_Hassett , I like this idea. Don’t forget to vote like I did!
Just curious, how would you expect this to be represented/displayed within a column’s cell? A horizontal bar, split into different blocks of colours, representing the field’s options?
Thanks @Richard_Sather!
As rollups currently only support numerical values, I’m wondering whether there could be scope to expand this to support alphabetical values or even icon-based rollups. I think a traffic light system (

) would be particularly useful, as it provides an instant visual indication of status without relying on numbers.
In my use case, our main project represents the full NPI (New Product Introduction) process. Alongside this, we have dedicated Quality Testing, Quality Compliance and Content projects that branch off from the main workflow and are responsible for executing their respective workstreams. These are managed as custom task types and are multihomed back into the main NPI project, giving visibility of the overall outcome while allowing each team to manage its own execution independently.
Although I can report on the execution projects individually, those reports don’t provide the associated context from the main NPI project, so portfolio-level reporting loses that connection. This means stakeholders have to jump between multiple projects to understand the overall status of a product.
Being able to surface or roll up a single-select field (or its associated icon) at the portfolio level would bridge that gap, giving stakeholders a simple, high-level view of overall project health or quality status without having to navigate into each project individually. It would also make it much easier to monitor stage gate progress across multiple products, with visual indicators such as Pass/Fail or a traffic light status showing at a glance as these branched projects can affect our main timeline.
Hi @Rebecca_Hassett , thanks for the insight. Usually, my team and I carry out a discovery call over a live engagement to understand the need before we provide solutions but it might be worth mentioning that if you have a numerical rollup in a portfolio and want to apply a spreadsheet-like ‘conditional formatting’ to it, you could use Rules within the Portfolio to affect the value of a single-select field (which could have emojis for options), based on the number value of your rollup field.
The key is to use the ‘Number is’ condition within the Rule’s condition.
If I’ve misunderstood your intention, hopefully I’ve at least provided a useful tip 
1 Like
@Richard_Sather thank you for the insight! I will certainly look at that as it could be an option
1 Like