Hello everyone,
We’re excited to announce a powerful new way to manage your codebase at scale: dynamic, parameter-based portfolios are now available in SonarQube Cloud Enterprise!
The feature makes it significantly easier to get an aggregated view of the projects you care about. Now, you can create portfolios that automatically stay up-to-date based on project tags, a regular expression on project keys, or by selecting entire organizations.
What’s new?
-
Define portfolios using three new methods: by project tags, by organizations, or with a regular expression (RegEx) that matches project keys.
-
Automatic updates: Portfolios automatically add or remove projects as their tags or keys change. This ensures your view is always current without any manual intervention.
-
Enterprise-wide scope: Easily create a portfolio that spans multiple organizations within your enterprise to get a true top-level view of specific technologies, teams, or initiatives.
Where to find it
Navigate to your Portfolios page (e.g., by going to My Portfolios from the main header) and click Create Portfolio. You’ll see the new options to define your portfolio dynamically.
We believe this will make portfolios an even more powerful tool for understanding the health of your code in your organization. We’d love to hear how you plan to use dynamic portfolios! What kind of project groupings will you create first?
Please share your thoughts and use cases in the comments below! 
John
P.S.: Want to have a chat? Feel free to book a call with one of our Product Managers to share more about your use cases and needs: Calendar Booking Link
3 Likes
Its great to see this feature coming now ! But i found some bug/s now. Main summary page of all portfolio don’t show any number. it shows error that no project is added in portfolio.
also suggesting small improvements :
- I suggest to include only “main branch scanned projects” as mandate for all dynamic options. in case of BY TAG or BY ORG , we can easily understand quick summary on main page - how many projects by TAG or in ORG and how many SCANNED. so risks data is only for SCANNED projects.
- By TAG , can we have “include tag” and “exclude tag” option too, so if we have one primary TAG but we need to exclude few of them using another tag, we can do that
3. BY ORG , we have ~12K projects now. So having 5000 limit is not worth. IF we have auto filter at backend that, only SCANNED project will be consider , that will be good.
4. BY Security Category ( example : authentication category) , this will help to understand, how many projects has risks related to authentication issues.
- By Severity = This help to focus on BLOCKER and Critical severity risks and understand how many projects has these two level of risks.
Looking for improvements and bug fix 
this is great feature although.
2 Likes
Hi @shrikantgade ,
Thank you for this feedback! We’ll dig into what’s happening.
John
A fix has been applied and is now live. Thank you for pointing this out @shrikantgade !
Yes. i can see it. its FIXEd. thanks for quick fix. One q = these summary number / rating on main page for a portfolio , is it for NEW CODE or OVERALL CODE ?
Hi @shrikantgade,
Let me know if I understood your question correctly or not, but on the Portfolio Overview, you can see both:
In the Portfolio Breakdown, you can switch tabs to see one or the other:
Or were you referring to a different view?
