Hi
Any updates in this Case, it is really required.
Thanks.
Hi @miq ,
Can I check if you were the one who created these items, you mentioned that the devs have said that they never received emails, were these items they “assigned” to themselves or issues that they created? Are they experiencing this issue also when someone else is assigning items to them?
As Ann has mentioned there is some confusion in this area, I am looking into the logs on our side, could you potentially message me privately with some of the emails that you would have expected to receive emails to? I would like to see if they are being deliberately ignored.
As I understand you would expect that these emails should be sent out to you for all instances described below:
- I create a new issue and it is auto-assigned
- I assign an issue to myself
- Another user assigned an issue to me
- General issues about the quality gate which were created by my changes
- General issues about the quality gate which were created by my colleagues changes
Having investigated this previously I know that Sonarcloud is currently filtering issues for items you create yourself. However I’m aware that this is not “obvious” and potentially the opposite of what you would desire this functionality to do.
ps. I realize I am covering many questions Ann has mentioned however I would like to investigate the issue and also fully build a picture of what you are looking for so that we might raise a request for changes moving forward. If there are bugs we will of course try and resolve them as a priority, however, changes as you would expect would need to be properly prioritized.
Hi @miq,
I can confirm that within the code the following items will always not receive emails:
Notification of which the change author is the assignee of all changed issues
Notification to users of the changes they made themselves
Where I would expect you to recieve emails:
Changes to the QualityGate on the main branch (main/master etc)
New Issues are being created on the main branch
New Issues are being assigned to you on the main branch
Failures in the analysis (unknown causes)
Here you can see some examples of the emails that I was able to create using a project
Finally, it is worth noting that I would have expected the following conditions to send emails, however, they did not, I would need to investigate this further:
Changes to QualityGate on a branch / PR
New issues being assigned to you on a branch / PR
So the developers will only receive a notification when the master branch is scanned and new issues is observed . Scanning performed on feature and Hotfix branches will not send at notification.
Yes, as I have been informed and also from what I can see in the code currently only notifications for the main branch and long-term branches will be produced. In the case of features and bugfixes by default, these will not be included.
In terms of branches which will be assessed you can see these in the branches section of the project.
Here you can see that I have main and branch-new. I would expect to recieve messages from both of these. You can also modify which branches you can receive these on by editing the long-lived branches pattern at the top right of the screen. In the case of long-term projects or branches you can then have teams collaborating on branches receive these notifications.
One thing to consider in this case is that any pipelines you are running would need to make sure they are running for these branches (I had to edit my own as I was working with only main and prs).
I hope this helps
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.