-
Notifications
You must be signed in to change notification settings - Fork 150
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
Add template id for azure devops bug filing #711
Comments
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! |
Hi @cnamal thanks for your interest in Accessibility Insights! This is an interesting suggestion. Adding a tag could be done by creating an additional text field in settings for tags. Using a template each team has defined might be possible but requires additional investigation. We are marking this request as help wanted. |
This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights! |
hey, I can work on this issue. Can you assign me? |
I noticed you added the button to file an issue on Azure DevOps directly through Accessibility Insights, which is awesome! 😊
We have to add the a tag for A11y Insights bugs and make them P0, and so I was wondering if it would be possible to provide a bug template id in the settings UI.
For reference, we have an ADO dashboard that has links to create bugs with correct information, such as
https://<obfuscated>.visualstudio.com/<obfuscated>/_workitems/create/Bug?templateId=<obfuscated>&ownerId=<obfuscated>
where templateId is a GUID. (I believe you can disregard the ownerId)
The text was updated successfully, but these errors were encountered: