app icon indicating copy to clipboard operation
app copied to clipboard

Unable to map Issue (testomatio) with bugs (Azure)

Open prajapatimurli opened this issue 1 year ago • 2 comments

Describe the bug We are following custom scrum process in Azure, Whenever we are raising issue in testomatio, it is showing error code - Not Found (HTTP 404) VS402323: Work item type Issue does not exist in project {id} or you do not have permission to access it.

on

To Reproduce Steps to reproduce the behavior:

  1. Login in Testomatio with valid credential
  2. Click on Test and expand test case
  3. Click on Link to Issue
  4. See error(Screenshot)

Expected behavior Issue should map with existing bug(type in azure)

Screenshots Kindly find attached screenshot

Desktop (please complete the following information):

  • OS: Windows 1 pro
  • Browser chrome
  • Browser Version 124.0.6367.62
  • Application: Dev

Additional context Mapping perfectly if project created in azure with process type Basic error_1jyo2hc

prajapatimurli avatar Apr 26 '24 05:04 prajapatimurli

@Fro0z1k any update on this?

prajapatimurli avatar May 02 '24 05:05 prajapatimurli

@prajapatimurli that is planned for next sprint, which will be delivered approximately in 2-3 weeks

poliarush avatar May 02 '24 08:05 poliarush

@poliarush any update on above?

prajapatimurli avatar May 23 '24 05:05 prajapatimurli

no, we have other items in our backlog right now, didn't have chance to look at it so far, you should wait a bit more on this

poliarush avatar May 24 '24 17:05 poliarush

Screenshot 2024-06-19 at 12 41 16

Fro0z1k avatar Jun 19 '24 09:06 Fro0z1k

Kindly close this. Wrongly reopened

prajapatimurli avatar Jun 24 '24 07:06 prajapatimurli

Hi @prajapatimurli! Thank you for the update 🙏 Could you please tell if the issue was fixed with the latest testomat update or if you managed to fix it on your side somehow?

TetianaKhomenko avatar Jun 24 '24 07:06 TetianaKhomenko

Hi @prajapatimurli! Thank you for the update 🙏 Could you please tell if the issue was fixed with the latest testomat update or if you managed to fix it on your side somehow?

@TetianaKhomenko I have manually configured it in Azure and able to raise bugs. I will check and update soon for recent update.

prajapatimurli avatar Jun 24 '24 08:06 prajapatimurli