You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The integration seems to work fine in the current version of Unity DevOps Version Control (previously PlasticSCM), but there is some behaviour that seems unintended.
My setup:
Logged into Unity Version Control with my Unity ID, with email address A.
Codecks account uses email address B. I entered this into the Preferences > Issue Trackers window inside UVCS/Plastic according to the image shown at point 4 of Getting Started in the integration readme.
The integration seems to attempt to fetch the task data from Codecks using email address A, instead of email address B. It then returns an error, stating "Failed to find user by mail: [email address A]". I believe that the integration should not be using email address A here, but instead should use email address B as entered in the Preferences > Issue Trackers window.
My colleague uses only 1 email address for all of this, and for him the integration works as expected.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
The integration seems to work fine in the current version of Unity DevOps Version Control (previously PlasticSCM), but there is some behaviour that seems unintended.
My setup:
Logged into Unity Version Control with my Unity ID, with email address A.
Codecks account uses email address B. I entered this into the Preferences > Issue Trackers window inside UVCS/Plastic according to the image shown at point 4 of Getting Started in the integration readme.
The integration seems to attempt to fetch the task data from Codecks using email address A, instead of email address B. It then returns an error, stating "Failed to find user by mail: [email address A]". I believe that the integration should not be using email address A here, but instead should use email address B as entered in the Preferences > Issue Trackers window.
My colleague uses only 1 email address for all of this, and for him the integration works as expected.
Thanks in advance!
The text was updated successfully, but these errors were encountered: