Your version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:
Thank you for the quick response. This is the Production SonarQube instance in the company I work for. We have just recently upgraded to this version and do plan on upgrading again next year but due to the number of customer accounts using the service and the various restrains arising from that, it will be at least a few months before its possible to schedule another upgrade.
I understand our version is past EOL, if someone could just let me know if what I’m asking is possible or not, on our current version, that would be much appreciated.
If not, I understand. We will try to upgrade as soon as possible regardless.
“New” metrics aren’t available to Portfolios. There were qualms here around how to measure that since each underlying project was likely to have a different definition of ‘new’. We worked past that when we created Applications, but have never revisited that in Portfolios, frankly because no one has ever asked for it.
Thank you for clarifying that for me. Its very much appreciated.
It makes sense that aggregating the new code metrics from projects might not be so straight forward since new code can have different definitions depending on the project configuration.
Its good to have clarity on this at least as it is something I was trying to implement for a customer but wasn’t sure if it was possible or not.
Maybe something for SonarQube to consider in a future version .