Since we use a common framework of software and we want to do a single scan per repo and we do not want to repeat scans in separate projects. So, I created the Portfolio level to hold all the common framework component repos. But for this set of shared components, there is not single “app” there are many and we don’t really want to try to track issues per application in this case. Just for the entire set of components.
So, in this case, it seemed a good fit to just use the automatic assignment feature and all of these projects are auto-added into the framework portfolio using wildcard. This worked so well in fact there was no need to create any “app” since clicking on the portfolio listed all the per-component projects for that common framework of software.
Since the software seems to allow all filters/queries at any level project, app, portfolio. I though there was no need. After realizing the new issues query (and only the new issue query) did not work, I simply created an Application that holds the same set of projects. Unfortunately the same wildcard feature does not exist for Application that does for Portfolios so I just had to add them using the pick list widget.
Overall, I find it odd that SonarSource would not want parity on these queries for portfolio, app, and project levels and the REST API and Web Interface all point to you being able to run the new issue query. It just seems like consistency would be better even if the query were a bit slower. But if the lack of this query is mentioned in the API and not present on the web interface, that would at least help.