Azure-devops-docs: Trello Service Hook appears to be broken for 2017 and below now

[nschonni]

Although it ships with the product, it doesn't appear possible to configure the hook anymore. This is kind of a product bug, but reporting it here since the documentation should probably be updated to reflect the support doesn't exist anymore.

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1402b59d-915f-2457-e198-60898fd66191
• Version Independent ID: af8951ef-3bc1-8748-81a5-03696c6f5e85
• Content: Trello with VSTS
• Content Source: docs/service-hooks/services/trello.md
• Product: devops
• GitHub Login: @elbatk
• Microsoft Alias: elbatk

[elbatk]

Thanks @nschonni , @willsmythe is this the case?

[nschonni]

@willsmythe can you confirm that the API changed on the Trello side and it isn't supported on the older versions so the docs can be updated

[nschonni]

@elbatk @willsmythe this is still an issue

[elbatk]

Hey @nschonni , going to try to bring in @roofers to help here as he looks over the Service Hooks now!

[roferg]

@nschonni - There was an issue with Trello in TFS 2017. It was around supported SSL versions. Can you open a customer support ticket and we'll be able to help get you unblocked.

[elbatk]

@roofers is there anything I should add to the docs or are we okay?

[nschonni]

Thanks @roofers we're trying to just get our folks to use TFS right now, but if there is a documentation update (even if it is "open a support ticket if it isnt' working") that would be good to add here. I think there are a bunch of social.msdn & SO threads with people hitting this and giving up :wink:

[roferg]

@nschonni - Yep. I'm going to work with @elbatk to get that added.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jean]

Anything happened? Was that "customer support ticket" created?

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.