In my company, all the source code is on the same project "SourceHub" and each team has its own project where they manage their WorkItems how they want.
This means that we have in our project some WorkItem types that don't exist in the SourceHub project.
Our Azure team is not really fan of adding all types for all teams to SourceHub, as it can quickly be a big mess.
When configuring the WorkItem Updater task with the pipeline UI, the "WorkItem types" field lists only the types from the current project, so it doesn't list all the types we use.
So, when we run the task, the WorkItem is properly found, but skipped as it is filtered because it doesn't have the proper type:
Could you provide a solution for this ?
Either:
Allow to select a different project for the WorkItem types list
Allow to edit manually this list to add custom types (EditableOptions = True ?)
Logikoz
commented
1 year ago
Hello !
In my company, all the source code is on the same project "SourceHub" and each team has its own project where they manage their WorkItems how they want. This means that we have in our project some WorkItem types that don't exist in the SourceHub project. Our Azure team is not really fan of adding all types for all teams to SourceHub, as it can quickly be a big mess.
When configuring the WorkItem Updater task with the pipeline UI, the "WorkItem types" field lists only the types from the current project, so it doesn't list all the types we use. So, when we run the task, the WorkItem is properly found, but skipped as it is filtered because it doesn't have the proper type:
Could you provide a solution for this ? Either: