My vision of the feature would be to allow agent to create a bug/task in Azure DevOps, based on the ticket that was raised in UseResponse, so directly in the UseResponse platform. The agent, from the UseResponse platform, should be able to see the status of the element that was created in DevOps, but this should not be made visible to the end user who raised the ticket as it is part of the internal process of the company.
Thanks!
Jonathan
Hello Stas,
My vision of the feature would be to allow agent to create a bug/task in Azure DevOps, based on the ticket that was raised in UseResponse, so directly in the UseResponse platform. The agent, from the UseResponse platform, should be able to see the status of the element that was created in DevOps, but this should not be made visible to the end user who raised the ticket as it is part of the internal process of the company.
Hi, DB is already a customer and it would be very valuable for us to have an integration of UseResponse and Azure DevOps. The integration would have to provide the same functionality as the integration of UserVois and Azure DevOps.
Hi, DB is already a customer and it would be very valuable for us to have an integration of UseResponse and Azure DevOps. The integration would have to provide the same functionality as the integration of UserVois and Azure DevOps.
At least 10 enterprise customers should request it or 20 basic customers or 15 basic customers and 5 enterprise customers. That way we get it into the next stage to review request and discuss in dev team - then we see if it's reasonable or not.
Also there is an option to share costs between 2-3 customers to cover development in order to start the process. We roughly estimate it now to cost about $3600.
At least 10 enterprise customers should request it or 20 basic customers or 15 basic customers and 5 enterprise customers. That way we get it into the next stage to review request and discuss in dev team - then we see if it's reasonable or not.
Also there is an option to share costs between 2-3 customers to cover development in order to start the process. We roughly estimate it now to cost about $3600.
We've tested it in cloud, and now it's in beta. Available to limited number of customers only, but you can test it with self-hosted. It should work as API methods are likely the same.
We've tested it in cloud, and now it's in beta. Available to limited number of customers only, but you can test it with self-hosted. It should work as API methods are likely the same.
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
Hi Jonathan,
Could you please describe your vision of the integration in more details?
What features for integration are required by your organization?
Hi Jonathan,
Could you please describe your vision of the integration in more details?
What features for integration are required by your organization?
Hello Stas,
My vision of the feature would be to allow agent to create a bug/task in Azure DevOps, based on the ticket that was raised in UseResponse, so directly in the UseResponse platform. The agent, from the UseResponse platform, should be able to see the status of the element that was created in DevOps, but this should not be made visible to the end user who raised the ticket as it is part of the internal process of the company.
Thanks!
Jonathan
Hello Stas,
My vision of the feature would be to allow agent to create a bug/task in Azure DevOps, based on the ticket that was raised in UseResponse, so directly in the UseResponse platform. The agent, from the UseResponse platform, should be able to see the status of the element that was created in DevOps, but this should not be made visible to the end user who raised the ticket as it is part of the internal process of the company.
Thanks!
Jonathan
Is the current implementation in UR Version 6.7.0 only for Azure DevOps Cloud or for onprem DevOps Server?
Is the current implementation in UR Version 6.7.0 only for Azure DevOps Cloud or for onprem DevOps Server?
Replies have been locked on this page!