-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure DevOps integration requests #3004
Comments
From a first user and developer:
|
From another user:
|
From another user:
|
From prospect who started a chat on our marketing page:
|
I think that #3499 is a duplicate. This is a great tool and would love to see Azure DevOps integration added. Adding my +1 and will ask all the folks I know to also add a plus one to the main thread to show support. |
@sheldonhull please do! We'd love that! |
A user 🔒 writes:
|
A user (soon to be enterprise customer) 🔒 writes:
|
Stale issue |
Someone I did Sprint Poker outreach to:
|
@gcrickman please continue to log the feedback you here too. We want all the signal we can around this item |
A user 🔒 mentioned:
|
A user 🔒 mentioned while discussing Sprint Poker:
|
A signed enterprise trial 🔒 shared:
|
A user 🔒 writes:
|
A user 🔒 writes:
|
A user 🔒 says:
|
+1 to ADO integration |
Azure DevOps was one of the top most requested integrations from the Parabol Customer Feedback Survey 🔒. |
A user 🔒 asks:
|
Stale issue |
Still would like to see this so bumping with a comment. Azure DevOps isn't going away for a long while for most enterprises, despite the initial GitHub migration hype. |
You'll be happy to learn we're actively developing this integration now along with some pals from Microsoft. Please follow along here! |
Grooming: Closing this discussion issue as we've committed ourselves to action |
Hey @sheldonhull: we're looking for beta testers. Would you be interested in giving us some feedback and testing? May I ask you to reach out to love@parabol.co? |
Tracking requests and feedback for an integration with Microsoft Azure DevOps. Any details directly from users (leave comments!) or verbatim data from users as to what features they’re looking for in an integration only make this issue mucho more better.
The text was updated successfully, but these errors were encountered: