Skip to content
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

[BUG] Issue filling to ADO board for "Issue" work item type does not work #1363

Open
lisli1 opened this issue Jun 17, 2022 · 4 comments
Open
Labels
feature request New feature or request status: await community interest Waiting for community engagement to prioritize

Comments

@lisli1
Copy link
Contributor

lisli1 commented Jun 17, 2022

Describe the bug
A clear and concise description of what the bug is.
AI Win is unable to file bugs to an ADO project that uses the "Issue" instead of "Bug" work item type.

To Reproduce
Steps to reproduce the behavior:

  1. Open Accessibility Insights for Windows
  2. Scan any test app
  3. File a bug to an ADO project that uses Basic processes (uses "Issue" instead of "Bug" work item type)
  4. See error: Server error Invalid argument value. Parameter name: typeNames

Expected behavior
Should start creating an issue in ADO with pre-populated fields from AI Win

Actual behavior
Server error

Screenshots or .GIF
Screenshot of error message
image

Desktop (please complete the following information):

  • OS: [e.g. Windows 10 1809] (Get the version by running winver from the command line) Windows 11 Version 21H2 (OS Build 22000.739)
  • Accessibility Insights for Windows Version: v1.1.1934.01
  • Target Application: [e.g. Chrome, Wildlife Manager] Wildlife Manager
  • Target Application Version: [e.g. 22] 2.0

Additional context
Priority requested -
Add any other context about the problem here.
This was fixed in AI Web: microsoft/accessibility-insights-web#1009, microsoft/accessibility-insights-web#3874

@lisli1 lisli1 added the bug Something isn't working label Jun 17, 2022
@ghost ghost added the status: new This issue is new and requires triage by DRI. label Jun 17, 2022
@ghost ghost assigned lisli1 Jun 17, 2022
@lisli1 lisli1 added the status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. label Jun 17, 2022
@ghost ghost assigned asksep Jun 17, 2022
@ghost
Copy link

ghost commented Jun 17, 2022

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

@ghost ghost removed the status: new This issue is new and requires triage by DRI. label Jun 17, 2022
@lisli1 lisli1 assigned DaveTryon and asksep and unassigned asksep and lisli1 Jun 17, 2022
@DaveTryon
Copy link
Contributor

Changes in Web: microsoft/accessibility-insights-web#568

@ferBonnin ferBonnin added feature request New feature or request and removed bug Something isn't working labels Jun 21, 2022
@ferBonnin
Copy link
Contributor

changing to feature request based on today's conversation. We will triage on our weekly meeting

@ferBonnin ferBonnin added status: await community interest Waiting for community engagement to prioritize and removed status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. labels Jun 21, 2022
@ferBonnin
Copy link
Contributor

Adding some notes from the triage conversation:

  • To investigate: what is the default for new ADO teams?
  • leaving as await interest to understand how many users are impacted by this (first time we hear about it for Win)

Ideas:

  • we may be able to use API access to investigate the type but it would mean taking an additional dependency
  • We could add a setting for users to choose which type (preferred, needs design)
  • To also consider how to test / validate in E2E

workarounds

  • copy paste content
  • or add the option to file bugs in the instance

@DaveTryon DaveTryon moved this from Needs Triage to Old backlog in Accessibility Insights Jun 28, 2023
@DaveTryon DaveTryon moved this from Old backlog to Tabled in Accessibility Insights Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request status: await community interest Waiting for community engagement to prioritize
Projects
Development

No branches or pull requests

4 participants