v15.1.7 - Source task work-items State = Done but when migrated, target is coming across as CLOSED.

[NormanGarciaV]

Hi,

Something odd is going on. v15.1.7 seems to be working, but for some reason, the state of work-items are coming across from the wrong process template.

Both, source and target are SCRUM, but when the migration finish, the state field is coming with the AGILE values. I have spotted this in the TASK and PBIs. See screenshots.

Small browser is the target project.
any thoughts?

migration-3-StateRun.log

[MrHinsh]

Do you have a field map for State in the config?

[MrHinsh]

Then are there work items in the source that have that value?

Other than mappers we don't do any translation?

[NormanGarciaV]

Hi @MrHinsh

You were right about those values... I reviewed the process template configuration, it turns out, there was some custom states for a few work-items that I was not aware.

However.. I created those states in the target, and ran a clean migration from scratch, but the state of the PBIs, Bugs (perhaps other work-items types but have not checked them all yet) are still coming wrong.

[MrHinsh]

You are going to need to add a mapping for the old states to the new states.

[NormanGarciaV]

Makes sense, but still wondering where is it getting the ACTIVE state from, as the source is set as IN PROGRESS.

Would you mind telling me where in the config file I should do that? perhaps an example.
Would it be something like this:

"FieldMaps": [
{
"$type": "MultiValueConditionalMapConfig",
"WorkItemTypeName": "*",
"sourceFieldsAndValues": {
"State": "In Progress",
"State": "Done"
},
"targetFieldsAndValues": {
"State": "In Progress",
"State": "Done"
}
}

Just want to make sure I put the mappings in the right place.

Thanks.

[MrHinsh]

The only changes come from the field maps!