Tfs WorkItem Bulk Edit Processor

[MrHinsh]

This discussion is for questions, feedback, and community support related to the Tfs WorkItem Bulk Edit Processor.

Quick Reference

• Class Name: TfsWorkItemBulkEditProcessor
• Friendly Name: Tfs Work Item Bulk Edit
• Documentation: Tfs WorkItem Bulk Edit Processor

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[kapilkhub]

Hi @MrHinsh I was wondering if the tool can help in the scenario.
I am working with mapping Bug states. As you may know, Bug states are categorized as "Proposed","InProgress", "Resolved", "Completed", "Removed"

I have a state "Duplicate" , this state is available in both Source process and Target Process , however they are in different categories.
in Source, the "Duplicate" is in Resolved category, and in "Target" its in "Removed" category. Could you please help on how to tackle this?
I do not want to change anything in target process.

Please checkout the screenshot., thanks again for your help.

[MrHinsh]

The category is irrelevant to the value. It has no impact on the migration.

[kapilkhub]

As I am going through source code, I do not think, we are validating any sort of categories.. so it will work with TfsWorkItemMigrationProcessor without anything additional changes in config as long as target has all source values ? @MrHinsh @satano

[MrHinsh]

What do you mean by categories?

[kapilkhub]

hi, @MrHinsh , I meant states category for bugs... mentioned above like "Proposed","InProgress", "Resolved", "Completed", "Removed".

Thanks, for conforming categories are irrelevant in migration