TfsTeamSettingsProcessor , Capacity team in Sprints

[AviramDahan]

I found this JSON config settings, and I would like to inquire whether, after merging everything, I can simply rerun it with this additional JSON in my configuration.
Will the capacity, along with all users' details, hours, activity, days off, and more, be updated in the existing work items that have already been merged, or do I need to delete them all and migrate again?
(the team members' users exist in the active directory already.)

Source documentation: https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v2/Processors/TfsTeamSettingsProcessor/

{
  "$type": "TfsTeamSettingsProcessorOptions",
  "Enabled": enable,
  "MigrateTeamSettings": true,
  "UpdateTeamSettings": true,
  "PrefixProjectToNodes": false,
  "MigrateTeamCapacities": enable,
  "Teams": null,
  "ProcessorEnrichers": null,
  "SourceName": "sourceName",
  "TargetName": "targetName"
}

[MrHinsh]

This was a contribution from @v-wilock, @XREvo, @pietergheysens , and @GordonBeeming going back to 2016....

I believe that @mihirdilip may have added that functionality in 2022!

[mihirdilip]

@AviramDahan

Will the capacity, along with all users' details, hours, activity, days off, and more, be updated in the existing work items that have already been merged, or do I need to delete them all and migrate again?

It has been while since I have used this tool. I am afraid I cannot remember off top of my head, you will have to trial it out with your dry-runs on test org.

You might want to change enable to true for MigrateTeamCapacities on config snippet you have pasted above,
Please refer to #1117 & #1217 for config settings (working back in 2022 hopefully still relevant!)

[AviramDahan]

@mihirdilip
First of all, thank you for your response and assistance; I truly appreciate it. I have questions:

1. If I have already merged the work items, can I rerun the configuration by adding the following settings, and will it update the existing sprints?

2. Do you have an email, Discord, or WhatsApp where I can contact you for small questions regarding this feature?

[MrHinsh]

1. Yes, if the node exists it will add the meta data
2. You should tag them here...

[AviramDahan]

@mihirdilip \ @MrHinsh

{ "$type": "TfsTeamSettingsProcessorOptions", "Enabled": true, "MigrateTeamSettings": true, "UpdateTeamSettings": true, "PrefixProjectToNodes": true, "MigrateTeamCapacities": true, "Teams": null, "ProcessorEnrichers": null, "SourceName": "sourceName", "TargetName": "targetName" },

error:

[17:21:41 ERR] [v14.3.10] Unhandled exception! System.InvalidOperationException: There is no endpoint named [Source] at MigrationTools.Endpoints.EndpointFactory.CreateEndpoint(String name) in D:\a\1\s\src\MigrationTools\Endpoints\EndpointFactory.cs:line 55 at MigrationTools.Processors.Processor.Configure(IProcessorOptions options) in D:\a\1\s\src\MigrationTools\Processors\Processor.cs:line 63 at MigrationTools.Processors.TfsTeamSettingsProcessor.Configure(IProcessorOptions options) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\Processors\TfsTeamSettingsProcessor.cs:line 60 at MigrationTools._EngineV1.Containers.ProcessorContainer.Configure() in D:\a\1\s\src\MigrationTools\_EngineV1\Containers\ProcessorContainer.cs:line 61 at MigrationTools.MigrationEngine.Run() in D:\a\1\s\src\MigrationTools\MigrationEngine.cs:line 87 at MigrationTools.Host.ExecuteHostedService.<StartAsync>b__5_1() in D:\a\1\s\src\MigrationTools.Host\ExecuteHostedService.cs:line 38 [17:21:41 INF] [v14.3.10] Application is shutting down...