Issues closed in short lived branch, will it reflect in master branch?

SonarQube Cloud
1

We have a project called “ABC” with one long-lived branch as “master” and few short lived branches e.g. main-1.1

right now, our active version is main-1.1, which is the ongoing project. In this project we had several hundreds issues reported on the historical code, which we do not want to fix. hence we have closed them as wot fix it. Now, our question is, we want these status changes to be retained by Sonar cloud or transfer to the “master” project somehow, so that we do not need to look at the same old issues which we anyways decided not to fix it.

Is there a possibility to do such status update on master (based on main-1.1 project)? if yes, can you please let us know how to do it? if not, then can you suggest a process how we can prevent such (huge) duplicate work for every new version scan ?

2

I have requested a Snooze issue feature, in my case for the PRs: ack the issue but do not silence it forever. AFAIK there is no active work for this.

What we ended up doing is that for such issues, that we know we only want to silence temporarily but that should be fixed longer term is that we have a weekly pipeline that reset their status to Open.

In your case you might be able to use the API to get the list of issues in one branch and map them to the other branch.

3

HI,

Issues are synched from main to branches on branch creation (and not again). So you could mark these issues in the main branch.

Alternately, you could just ignore them altogether and focus on new code.

 
HTH,
Ann