title: SonarQube Issue Assign feature usage in SonarQube version 5.1
body: <p>I am trying to use Issue Assign feature of SonarQube 5.1 and configured it to assign all issues to author as determined by the SCM metrics.
  I am using SVN 1.6. When I run sonar analysis for a module, Sonar is able to identify issues but unable to assign them.</p>
  
  <p>Please find maven debug information:</p>
  
  <pre><code>[DEBUG] [16:31:35.845] Found new issue [afa5355b-16a0-4246-aefa-101e4470db7f]
  [DEBUG] [16:31:35.845] Configured auto-assign severity: INFO
  [DEBUG] [16:31:35.845] Issue afa5355b-16a0-4246-aefa-101e4470db7f severity: MAJOR
  [DEBUG] [16:31:35.845] Issue afa5355b-16a0-4246-aefa-101e4470db7f severe enough to auto-assign: true
  [DEBUG] [16:31:35.845] Found resource with key: [src/main/java/com/wcg/calms/xml/util/Persist.java]
  [DEBUG] [16:31:35.846] No measure found for metric [authors_by_line] on resource [src/main/java/com/wcg/calms/xml/util/Persist.java]
  [WARN] [16:31:35.846] Unable to assign issue [afa5355b-16a0-4246-aefa-101e4470db7f]
  </code></pre>
  
  <p>Could anyone please advise what is wrong? I am not sure how Sonar extracts SCM information from SVN. By the way, my svn and sonar user name are same.</p>