Open sjasani opened 7 years ago
In order to use the app against TFS on-premises you will need to enable basic authentication in TFS.
WARNING: Basic authentication sends username and passwords in plaintext. You should consider configuring TFS to use SSL in order to secure communication when using basic auth.
I am configuring this app with TFS 2017 on-premises and I would be very grateful if I could get more detailed instructions. For example, where exactly to put address of TFS server. Thanks.
When you are managing the app in Zendesk, you need to put the TFS base URL in the text box with the label Visual Studio Team Services account name
Instead of using a VSTS account name, use your TFS base URL.
https://www.visualstudio.com/en-us/docs/marketplace/integrate/service-hooks/services/zendesk
When I click on the ‘New Work Item’, it does create ‘issues’ correctly in our TFS server(On-Premise). Although I am not able to see them in the app in Zendesk. Error observed: Oops! Something went wrong while loading working items. Click the refresh icon to try again.
How to solve this? Do i need to enable any additional settings? Thanks
Typically this error is related with wrong TFS credentials. What credentials are you suing when prompted in the widget?
HI Bruno,
Thank you for the reply.
I got another problem, Recently we changed the 'configure the action' settings to use another Zendesk user to create an internal comment. Since then, the internal comment functionality is not working. I have tried using a new API token as well(Since the API token used for this Service hook was not showing active from the configuration change date). Still no internal comments. I am able to successfully link to the TFS items and see the recent HISTORY fields in the app. Any hints on how to proceed on this?
Thanks & Regards, Deepthi Chandran
On Mon, Feb 27, 2017 at 3:28 PM, Bruno Câmara notifications@github.com wrote:
Typically this error is related with wrong TFS credentials. What credentials are you suing when prompted in the widget?
[image: image] https://cloud.githubusercontent.com/assets/822851/23364910/d094cef2-fcf8-11e6-9473-e701a6ba1900.png
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Microsoft/vsts-zendesk-app/issues/25#issuecomment-282735096, or mute the thread https://github.com/notifications/unsubscribe-auth/AM9NYyLVpyw41jGLQfNhRSZezcuX2Nzcks5rgt1zgaJpZM4KvLs3 .
Hi @chandrandpt
What do you see in the VSTS service hook subscription history? Any error?
Unfortunately no. History displays all attempts as successful from TFS side. But in zendesk the respective API is showing as not used.
On 27 Apr 2017 6:04 p.m., "Bruno Câmara" notifications@github.com wrote:
Hi @chandrandpt https://github.com/chandrandpt
What do you see in the VSTS service hook subscription history? Any error?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/vsts-zendesk-app/issues/25#issuecomment-297760077, or mute the thread https://github.com/notifications/unsubscribe-auth/AM9NYyUDHEVZ3M8jHYc-AE6UaYBPqrGKks5r0LyJgaJpZM4KvLs3 .
For "all attempts" you mean all Test attempts, i.e, you click on the TEST button?
The Test button doesn't trigger a call to Zendesk API. If you look at Request tab you will see the message "No Zendesk tickets found", so the test cannot be associated with any Zendesk ticket.
Unfortunately you will need to do a real test with a VSTS Work Item that is already associated with a Zendesk ticket by adding a comment on it.
We had a try with the TEST attempt as well as creating an actual comment on a TFS item. History shows the respective comment attempt as successful action. But it does not call the Zendesk API created for this Service Hook.
[image: Inline image 1]
Zendesk API:
[image: Inline image 2]
On Fri, Apr 28, 2017 at 9:42 AM, Bruno Câmara notifications@github.com wrote:
For "all attempts" you mean all Test attempts, i.e, you click on the TEST button?
[image: image] https://cloud.githubusercontent.com/assets/822851/25518926/a332b0cc-2bed-11e7-8bcf-e8787e6cb0b5.png
The Test button doesn't trigger a call to Zendesk API. If you look at Request tab you will see the message "No Zendesk tickets found", so the test cannot be associated with any Zendesk ticket.
[image: image] https://cloud.githubusercontent.com/assets/822851/25519144/93198be2-2bee-11e7-8ef8-005891dc9140.png
Unfortunately you will need to do a real test with a VSTS Work Item that is already associated with a Zendesk ticket by adding a comment on it.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/vsts-zendesk-app/issues/25#issuecomment-297930936, or mute the thread https://github.com/notifications/unsubscribe-auth/AM9NY6YZbKT4EjdIpH-Pj1w1x46C__L9ks5r0ZhkgaJpZM4KvLs3 .
I can't see your images. Could you fix them in order to see what you are trying to show?
Please also show your images from the "Request" tab. The TFS Work item that you are using for your tests needs to be linked with a Zendesk ticket, otherwise a call to Zendesk API won't be made.
Request tab did not show any tickets linked to it, after a bit more troubleshooting we realised that there was a mistake in the Account Name configured in the service hook. Now all working flawless. Thank you for the help. :)
hi
Can i get some help on this...I still cannot get this working....
Have setup the hook in VSTS with the account details as in Zendesk but the comments from VSTS arent going through..
Currently this solution only seems to be compatible with Visual Studio Team Services. Is there a workaround available, or plans to support on-prem TFS in the future?