Comments (13)
FYI the reference name for the field is "Microsoft.VSTS.Common.AcceptanceCriteria".
Can you share your config.json
file?
from jira-azuredevops-migrator.
Potentially related to #851?
from jira-azuredevops-migrator.
Sure,
That's my config file.
{
"source-project": "COE SOFTWARE",
"target-project": "AMS SES",
"query": ""Epic Link"=SW-57991 and issue in(SW-59066, SW-58880) ORDER BY rank",
"using-jira-cloud": true,
"workspace": "C:\Temp\JiraExport\",
"epic-link-field": "Epic Link",
"sprint-field": "Iteracion",
"download-options": 7,
"batch-size": 20,
"log-level": "Debug",
"attachment-folder": "Attachments",
"user-mapping-file": "users.txt",
"base-area-path": "AMS SES",
"base-iteration-path": "AMS SES",
"ignore-failed-links": true,
"include-link-comments": false,
"include-jira-css-styles":false,
"process-template": "Custom-agile",
"link-map": {
"link": [
{
"source": "Epic",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Parent",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Relates",
"target": "System.LinkTypes.Related"
},
{
"source": "Duplicate",
"target": "System.LinkTypes.Duplicate-Forward"
}
]
},
"type-map":{
"type": [
{
"source": "Feature",
"target": "Feature"
},
{
"source": "Epic",
"target": "Epic"
},
{
"source": "Story",
"target": "User Story"
},
{
"source": "Bug",
"target": "Bug"
},
{
"source": "Task",
"target": "Task"
},
{
"source": "Sub-task",
"target": "Task"
}
]
},
"field-map": {
"field": [
{
"source": "summary",
"target": "System.Title",
"mapper": "MapTitle"
},
{
"source": "assignee",
"target": "System.AssignedTo",
"mapper": "MapUser"
},
{
"source": "description",
"target": "Microsoft.VSTS.Common.AcceptanceCriteria",
"mapper":"MapRendered"
},
{
"source": "priority",
"target": "Microsoft.VSTS.Common.Priority",
"mapping": {
"values": [
{
"source": "Blocker",
"target": "1"
},
{
"source": "Critical",
"target": "1"
},
{
"source": "Highest",
"target": "1"
},
{
"source": "Major",
"target": "2"
},
{
"source": "High",
"target": "2"
},
{
"source": "Medium",
"target": "3"
},
{
"source": "Low",
"target": "3"
},
{
"source": "Lowest",
"target": "4"
},
{
"source": "Minor",
"target": "4"
},
{
"source": "Trivial",
"target": "4"
}
]
}
},
{
"source": "Sprint",
"source-type": "name",
"target": "System.IterationPath",
"mapper": "MapSprint"
},
{
"source": "labels",
"target": "System.Tags",
"mapper": "MapTags"
},
{
"source": "comment",
"target": "System.History",
"mapper":"MapRendered"
},
{
"source": "status",
"target": "System.State",
"for": "Task",
"mapping": {
"values": [
{
"source": "To Do",
"target": "To Do"
},
{
"source": "Done",
"target": "Done"
},
{
"source": "In Progress",
"target": "In Progress"
}
]
}
},
{
"source": "status",
"target": "System.State",
"for": "User Story, Epic",
"mapping": {
"values": [
{
"source": "Parking Lot",
"target": "Backlog"
},
{
"source": "New",
"target": "Backlog"
},
{
"source": "Pending Grooming",
"target": "Requeriment"
},
{
"source": "Ready",
"target": "Requeriment"
},
{
"source": "Ready for DEV",
"target": "Requeriment"
},
{
"source": "Development",
"target": "Active"
},
{
"source": "Build Installed",
"target": "Active"
},
{
"source": "Certification",
"target": "Active"
},
{
"source": "Done",
"target": "Done"
},
{
"source": "Approved",
"target": "Done"
},
{
"source": "Closed",
"target": "Closed"
},
]
}
},
{
"source": "status",
"target": "System.State",
"for": "Feature",
"mapping": {
"values": [
{
"source": "To Do",
"target": "New"
},
{
"source": "Done",
"target": "Done"
},
{
"source": "In Progress",
"target": "In Progress"
}
]
}
},
{
"source": "Story Points",
"source-type": "name",
"target": "Microsoft.VSTS.Scheduling.Effort",
"not-for": "Task"
},
{
"source": "remainingEstimate",
"target": "Microsoft.VSTS.Scheduling.RemainingWork",
"for": "Bug,Task"
},
{
"source": "description",
"target": "Microsoft.VSTS.TCM.ReproSteps",
"for": "Bug"
}
]
}
}
from jira-azuredevops-migrator.
In addition if I use the description field the images don't break.
from jira-azuredevops-migrator.
Looks like the attachment path correction is only implemented for Description, Repro Steps and Comments as of today. Let me create a fix and upload a build for you to try out @diegoq. I will get back to you with a build soon!
from jira-azuredevops-migrator.
Debug.zip
@diegoq Try this build and let me know the results!
from jira-azuredevops-migrator.
@Alexander-Hjelm Debug zip doesn't have the wi-import exe.
from jira-azuredevops-migrator.
You are correct, use this one
from jira-azuredevops-migrator.
Hi @Alexander-Hjelm, now the jira-export is missing.
from jira-azuredevops-migrator.
Use both of the above zips! One contains the exporter and one the importer
from jira-azuredevops-migrator.
Ok Let me do it
from jira-azuredevops-migrator.
@Alexander-Hjelm yes Those zips work! so what's the next step?
from jira-azuredevops-migrator.
Perfect! :)
The bundles I sent you are based on the main line, so you already have the latest version of the tool. Continue using that until we have released the next version with these changes incorporated.
Merging the PR will close the issue. Feel free to reopen it and tag me if the problem persists!
from jira-azuredevops-migrator.
Related Issues (20)
- configuring "for" and "not-for" for field mapping HOT 3
- Attachments not getting rendered properly in the comments in Azure devops after migration HOT 6
- Parent - child relation - not mapped correctly HOT 10
- Custom Field in Jira not exporting the data correctly, fields missing in export HOT 26
- 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
- All Images shown as 'broken image' icon. (And if I can access them, they images have a Jira URL) (same Issue as #887?) HOT 3
- Add a way to include a Default value in a field map.
- Multiple fields found for assignee. Selecting customfield_24863. HOT 6
- Migrating test details(design steps, test runs, test plans and so on) from Cloud JIRA with X-Ray to Azure HOT 15
- jira-export- not able to fetch the project name, even if it exist HOT 9
- [JMOSS+JMP] Bump Newtonsoft.json + Restsharp
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.