Workitem processor error "Credential scanning detected secret(s)."

[madhuripawar2212]

During workitem migration, the processor is thowing me the attached error. I did check the workitems individually, there are not confidential information.

[MrHinsh]

The confidential information must be in the history.

We have a new string manipulator feature in v15 that would allow you to remove the offending data from the description.

If you check through the history of the description field you should see where it is! The log should also say which revision it was migrating.

[madhuripawar2212]

I have it as it shows here https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v1/

I have the code before the processor. Something like below

"CommonEnrichersConfig": [
{
"$type": "StringManipulatorEnricherOptions",
"Enabled": true,
"MaxStringLength": 1000000,
"Manipulators": [
{
"$type": "RegexStringManipulator",
"Enabled": true,
"Pattern": "[^( -~)\n\r\t]+",
"Replacement": "",
"Description": "Remove invalid characters from the end of the string"
}
]
}
],

[MrHinsh]

You need the v15.0 version

[madhuripawar2212]

When I try to upgrade it, Its not giving me 15 version

[MrHinsh]

[MrHinsh]

Check "%Localappdata%\Microsoft\WinGet\Packages"... I just ran the update and got v15.0.0

[madhuripawar2212]

[madhuripawar2212]

I can see everything is mapped in the logs. Is there a way we can skip the history?

[MrHinsh]

No. This seams like a bug thugh!

[madhuripawar2212]

Oh okay. Will this is be looked at soon?

[MrHinsh]

I validated that the mapping all works in our test environment.

Easiest way to see why it's not doing what it's supposed to is to run that work item in Visual studio and see why!

It could be capitalisation or other reasons.

I'm in Seattle for the next week

[MrHinsh]

@madhuripawar2212 you could try a different mapping?

"^OldProjectName([\\\\]?.*)$": "NewProjectName$1",

or

"^OldProjectName([\\\\]?.*)$": "NewProjectName",

The first one maps all OldProjectName area or iterations to a similar new node. If you have CreateMissingNodes enabled then it will then create that.

The second will just map all OldProjectName to the new project name root.