Comments (3)
Alexander-Hjelm
commented on June 5, 2024
Hi @ankusinha23 !
We would need to look closer at your config.json file to say for sure what the issue is, but it seems that you have multiple mappings set up for AppectanceCritera and ReproSteps, and it seems like multiple mappings for the same field are acting on the same WorkItemType.
In general, for and not-for refers to the ADO Work Item Types. for will apply the mapping to any work item with any of the specified types, and not-for will apply the mapping to any work item which does not belong to the specified types.
I hope that shed some light on your situation. Otherwise you are welcome to attach your config file here.
from jira-azuredevops-migrator.
github-actions
commented on June 5, 2024
This issue is stale because it has been open for 25 days with no activity.
from jira-azuredevops-migrator.
github-actions
commented on June 5, 2024
This issue was closed because it has been inactive for 5 days since being marked as stale.
from jira-azuredevops-migrator.
Related Issues (20)
- Link to source Ticket in Jira HOT 4
- JIra Key not found exception HOT 3
- WorkItems get repeat after importing second time HOT 2
- Update HOT 1
- Custom fields assigned a value on creation and not changed are not exported HOT 10
- why we are using revsions while migration .. instead we could have used jira api which just fetches info straightforward HOT 1
- Mapping Jira Custom Fields to Azure DevOps History HOT 11
- Import all the fields of Test case instead of few fields. HOT 1
- Is there a version of application which is supporting Jira with extension structure HOT 15
- Development / Releases are supported? HOT 6
- show round time in effort field HOT 12
- Jira Users are not getting migrated HOT 1
- Description Field Blank in ADO User Story HOT 3
- Flat Migration HOT 3
- Add support for development links to non-migrated GitHub repositories
- Support for Continuing an Import at a Specific Revision HOT 4
- Best way to migrate large amount of issues HOT 14
- how can I use the tool if I have issue types Test and Test Plan and I don't have Task or sub task or any issue types else on jira ? HOT 1
- Linked issue is lost during the import/export process HOT 1
- Workitem Linking not working as expected HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jira-azuredevops-migrator.