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

Support Team-specific Backlogs (Area Paths) when creating ADO work items #899

Open
gemgit7 opened this issue Jan 8, 2022 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@gemgit7
Copy link

gemgit7 commented Jan 8, 2022

Describe the problem

If there are multiple Azure DevOps Teams defined in the same Project and it has multiple Backlogs, CxFlow (in the webhooks mode) currently does not allow creating workitems in a Backlog that belongs to a specific Team.

For example, if an ADO project 'SCA' has multiple teams/area paths (ex. 'Resolver', 'UI', 'XYZ'), and each team has a corresponding Backlog, CxFlow users cannot specify which Backlog to create the WorkItems under.

Proposed solution

The alt-fields configuration parameter is available for the command-line execution mode via the parameter '--alt-fields'. In the webhooks mode, however, this configuration element is not available to be set by way of configuration.
A possible solution is to support the 'alt-fields' (custom fields) configuration element in ADO config-as-code. This can be used to specify the ADO "System.AreaPath" attribute value - which can then be used by the ADOIssueTracker to create the CreateWorkItemAttr object and add it to the body before calling the Create Work Item ADO REST API.

Please treat that proposed solution with a grain of salt - it's just a thought :)

Additional details

for (Map.Entry<String, String> map : request.getAltFields().entrySet()) {

@gemgit7 gemgit7 added the enhancement New feature or request label Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant