- ALM used (Azure DevOps)
- CI system used (Azure DevOps)
- Languages of the repository - Csharp
- Error observed
New issue is getting assigned to a comitter before last committer - Steps to reproduce
- User 1 : Creates a branch (might have old code smells)
- User 2 : makes a mistake and commits with new codesmell, say CS1
- SonarCloud analysis is done, identifies CS1 and old code smells say CS44, CS45
4. Assigns CS1 to User 2 and CS44 & CS45 to User 1 - Node CS44 and CS45 were introduced by some other user in past, say User 0
Is #4 expected behaviour? Should it assign issue to User 0 instead of User 1?