You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
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
cx-flow/src/main/java/com/checkmarx/flow/custom/ADOIssueTracker.java
Line 251 in 64ae217
The text was updated successfully, but these errors were encountered: