microsoft / microsoft/process-migrator
Field name case sensitive - Source and Destination
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
I had a case where a field name was like below:
Source - "Working with"
Destination - "Working With"
The import gave me an error as it was unable to create the field as Azure DevOps see it as the same field but apparently the migratory doesn't and so tried to create a new one.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified in the report. Reproduce the import with the differently cased “Working with” and “Working With” fields, then verify that matching Azure DevOps field names no longer causes an attempted duplicate creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100