Hi Jonathan, Unfortunately this extension is not supported at the moment, but we are hard at work on a new version which is scheduled to be released mid next year. The new version will address these issues.
Hi Jonathan, When using Git, the email used for the commit can be different than the email used for VSTS authentication. The pull requests are created with VSTS credentials which is why you see them. This can happen when you use one email for GitHub and another one for VSTS. In Visual Studio you can change the email via Team Explorer tab | Settings, Global/Repository Settings, Email Address. When integrated VSTS in TimePro, VSTS APIs didn't have a reliable way to get all of the commits of a user regardless of what email they used in Git. We'll investigate if the VSTS APIs have addressed this issue. If you need more help, sent us an email to info@ssw.com.au and we'll get in touch.
Hi Jonathan, Unfortunately this extension is not supported at the moment, but we are hard at work on a new version which is scheduled to be released mid next year. The new version will address these issues.
Hi Jonathan,
When using Git, the email used for the commit can be different than the email used for VSTS authentication.
The pull requests are created with VSTS credentials which is why you see them. This can happen when you use one email for GitHub and another one for VSTS.
In Visual Studio you can change the email via Team Explorer tab | Settings, Global/Repository Settings, Email Address.
When integrated VSTS in TimePro, VSTS APIs didn't have a reliable way to get all of the commits of a user regardless of what email they used in Git.
We'll investigate if the VSTS APIs have addressed this issue.
If you need more help, sent us an email to info@ssw.com.au and we'll get in touch.