For Support purposes but possibly for other use case it would be useful to distinguish projects (and potentially other objects) that were created through the migration tool vs the ones that were created through standard SQC workflows.
One idea is to include some sort of telemetry when a migrated project is pushed on the SQC side.
This can be achieved through 2 means:
For Support purposes but possibly for other use case it would be useful to distinguish projects (and potentially other objects) that were created through the migration tool vs the ones that were created through standard SQC workflows.
One idea is to include some sort of telemetry when a migrated project is pushed on the SQC side.
This can be achieved through 2 means:
analytics.pbadd aci_name=sonar-migration-toolentry - This was already implemented by fix: generate mandatory analytics.pb in fabricated scanner report #480linkin the SQC projects Links:- Name
SQS migrated project- Linking back to the original project URL. The original project URL should be like
<ORIGINAL_SQS_BASE_URL>/dashboard?id=<OriginalProjectKey>-