Repository navigation
Conversation
Collect Azure Boards work items, iterations, comments, and changelogs, and Azure Test Plans cases and executions, into the ticket and QA domains. Scope config can map Azure types and states, and comment and changelog collection stay optional. Work items and tests belong to the project. Collecting them on every selected repository would store the same rows once per repository, so the the plugin only collects the one board and QA project for first scope that requests them. Now the plugin does not show repositories that are disabled in Azure Devops. Additionally, a project with no repository now gets one "<project> (project)" scope, which the scope picker can select. Graph users are served by vssps.dev.azure.com. With recent changes in API client, it now rejects an absolute UrlTemplate, so the plugin now uses a second client for account collection with that endpoint and a relative path. The connection form now lists the Read scopes this plugin needs, so a user can easily create a token with necessary scopes. Additionally, username can now be left empty for Cloud (as was stated on the description of the field), instead of having to set a username with a whitespace to be able to save the connection. Refs apache#5996 Signed-off-by: Roger Abelenda <3179183+rabelenda@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Collect Azure Boards work items, iterations, comments, and changelogs, and Azure Test Plans cases and executions, into the ticket and QA domains. Scope config can map Azure types and states, and comment and changelog collection stay optional.
Work items and tests belong to the project. Collecting them on every selected repository would store the same rows once per repository, so the the plugin only collects the one board and QA project for first scope that requests them.
Now the plugin does not show repositories that are disabled in Azure Devops. Additionally, a project with no repository now gets one " (project)" scope, which the scope picker can select.
Graph users are served by vssps.dev.azure.com. With recent changes in API client, it now rejects an absolute UrlTemplate, so the plugin now uses a second client for account collection with that endpoint and a relative path.
The connection form now lists the Read scopes this plugin needs, so a user can easily create a token with necessary scopes. Additionally, username can now be left empty for Cloud (as was stated on the description of the field), instead of having to set a username with a whitespace to be able to save the connection.
Does this close any open issues?
References #5996 which is closed but it never merged the changes and was missing the Test Plans entities.
Screenshots