Activity
Newest
Oldest
G
Grant Owens
Not a Canny customer currently, but evaluating options. Integration with ADO would be a HUGE influencer to the product we ultimately choose. The two main features we'd want is 1) the ability to create features in ADO from within Canny (want to avoid copy / paste) and 2) ability for Canny to track ADO feature status.
C
Casey Zeman
Any updates on this one? When will it be getting launched.
N
Nicolas Kramer
A few thoughts from our side:
Main Goal:
The main goal would be to be able to translate (eg by linking) the voted feedback into actual features in ADO.
The purpose is to keep our stakeholders up to date in which of their voted feedback is included in what feature, and in what stage that feature is.
The stage details come from ADO. There a feature has a status (import into Canny?), an Itteration Path, which usually has dates.
This would mean you need to be able to map the ADO statuses to the Canny statuses. Thats a simple many-to-one relationship.
In terms of "user stories" the above would mean.
As a feedback provider, I want to know if my feedback in planned into the program (ADO status).
As a feedback provider, I want to know when i can expect the delivery of my request (ADO status and iteration path changes)
I have no issue with manually creating items, and copy pasting content. But it is really cumbersome and error prone to have to update the status on both ADO and then Canny, to update your stakeholders.
Lastly, you need to account for several feedback entries to fit under a single ADO item. What if someone wants to link to epics in ADO? or what if a feedback is a smaller PBI (Product Backlog Item) or a bug.
Many canny entries could link to the same ADO entry.
Cheers,
Al Anderson
If each Board could have its own settings that would be ideal. Like Gregg B. Jensen mentioned one board may create Features, another may create Bugs. And it would be nice to control the 'Area' of new DevOps items on a per board basis.
The Ability to Create Work Items In DevOps (Features, Stories, Bugs) when a Feedback item is created. And a way to tell that item is 'linked' in both systems. There may be scenarios where we would like to sever the link.
Map statuses, and have statuses update in Canny when a DevOps work item status changes.
Update the DevOps Work Item discussion field with Canny 'Activity'
Track Votes in Canny, in a DevOps work Item.
G
Gregg B. Jensen
We would be looking to have a Feature Work Item created in Azure Dev Ops for each post on our Features board, and a Bug Work Item created in Azure Dev Ops for each post on our Bugs board. Then we would like the title, details, and comments to sync from both sides. It would also be important to be able to map status changes from Dev Ops to change the status of the post.
J
Jacques Snyman
My requirements are mostly the same as Kamal Saran's, however, I may not want new stories to automatically be added to a particular iteration path.
I should also be able to specify an area path per board.
Kamal Saran
from my perspective, I would like to integration to achieve below goals-
- Creating of user story/feature in Azure devops in particular Iteration path when new feedback entry on canny.
- Sync of user story status b/w 2 platforms
- Current Sprint stories appearing on canny roadmap view
- when I closed a user story in ADO then it should update canny and inform my voters.
- Nice to have some ID for each feedback entry so I can use that ID in ADO field. as of now I inserting feedback link. see attached snap..
Sarah Hum
under review
Hi all, we are considering building an Azure DevOps integration and need your input! We want to know how you'd like this integration to work. Please leave a comment or message us directly.
R
Reshma Mathew
Sarah Hum: Hi There, I'm not a user, I'm just leaving this comment hoping that you will find it useful. When I was vetting a feedback manager platform like Canny, I was also looking for a way to integrate with VSTS mainly because I wanted to find a way to link the feedback/ideas logged to the product backlog (managed in VSTS in my case). The stories from VSTS could show on Canny's admin panel so that feedback managers could also see the status of the user stories. What would be interesting is if there was a way to track if the user stories actually satisfied the feedback, but this may lead into product analytics.
Gregg B. Jensen
This is a critical integration for our organization as well.
Jan Bosch
We also using Azure DevOps and are looking for a feedback / ideas voting. Any news?
Load More
→