You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/config.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,6 @@ Currently the tool has a rather naive implementation for mapping certain constru
100
100
|MapArray|Maps an array by replacing comma with semi-colon|
101
101
|MapRemainingWork|Maps and converts a Jira time to hours|
102
102
|MapRendered|Maps field to rendered html format value|
103
-
|MapFieldsComposite|Maps multiple fields and concatenates the field values based on a user-defined pattern. In the `source` field, you must specify a pattern where any `${...}` tokens will indicate a field substitution. For example, use `${state}` to include the issue state in the mapped value.|
104
103
|(default)|Simply copies soure to target|
105
104
106
105
## Example configuration
@@ -186,7 +185,7 @@ Currently the tool has a rather naive implementation for mapping certain constru
186
185
{
187
186
"source": "description",
188
187
"target": "System.Description",
189
-
"mapper":"MapRendered"
188
+
"mapper":"MapRendered"
190
189
},
191
190
{
192
191
"source": "priority",
@@ -250,12 +249,7 @@ Currently the tool has a rather naive implementation for mapping certain constru
### 1. Convert Jira formatted descriptions and comments on migration
4
-
5
-
- With our latest release (2.3.1) we have introduced a new mapper called "MapRendered" that should be used when mapping fields to get the Html rendered value from Jira.
2
+
1. Convert Jira formatted descriptions and comments on migration
3
+
- With our latest release (2.3.1) we have introduced a new mapper called "MapRendered" that should be used when mapping fields to get the Html rendered value from Jira.
6
4
7
5
Example:
8
6
`{`
@@ -11,28 +9,25 @@ Example:
11
9
`"mapper":"MapRendered"`
12
10
`}`
13
11
14
-
### 2. Why I am getting Unauthorized exception when running export?
15
-
16
-
- It might be that you are using your email as a username, try to use your username instead of an email address.
12
+
2. Why I am getting Unauthorized exception when running export?
13
+
- It might be that you are using your email as a username, try to use your username instead of an email address.
17
14
- using Jira Cloud - it might be that you need to to use the API token as a password.
18
15
19
-
### 3. How to map custom field by name?
16
+
3. How to map custom field by name?
17
+
- To map a custom field by name we have to add a mapping in the configuration file.
20
18
21
-
- To map a custom field by name we have to add a mapping in the configuration file.
22
-
23
-
Example:
19
+
Example:
24
20
`{
25
21
"source": "CustomFieldName",
26
22
"source-type": "name",
27
23
"target": "Microsoft.VSTS.TCM.ReproSteps"
28
24
}`
29
25
30
-
### 4. How to migrate custom fields having dropdown lists?
31
-
26
+
4. How to migrate custom fields having dropdownlists?
32
27
- To map a custom field which is an dropdown list you can use MapArray mapper to get in a better way.
33
28
Also take a look at the other possible [Mappers](config.md#mappers) to use.
34
29
35
-
Example:
30
+
Example:
36
31
` {
37
32
"source": "UserPicker",
38
33
"source-type": "name",
@@ -42,11 +37,11 @@ Example:
42
37
}
43
38
`
44
39
45
-
### 5. How to migrate correct user from Jira to Azure DevOps and assign to the new work items?
40
+
5. How to migrate correct user from Jira to Azure DevOps and assign to the new work items ?
41
+
- User mapping differes between Jira Cloud and Jira Server. To migrate users and assign the new work items in Azure DevOps to the same user as the original task had in Jira, we need to add a text file in the root that would look something like this:
46
42
47
-
- User mapping differs between Jira Cloud and Jira Server. To migrate users and assign the new work items in Azure DevOps to the same user as the original task had in Jira, we need to add a text file in the root that would look something like this:
48
-
49
-
- When using Jira Cloud then firstly make sure in the config the '"using-jira-cloud": true' is set. The mapping file the should have accountId/email value pairs. To use email value pairs the users email should be set to public in the user profile in Jira Cloud. Otherwise the tool cannot get the email and will use accountId instead for mapping.
43
+
- When using Jira Cloud then firstly make sure in the config the '"using-jira-cloud": true' is set. The mapping file the should have accountId/email value pairs. To use email value pairs the users email should be set to public in the user profile in Jira Cloud
44
+
otherwise the tool cant get the email and will use accountId instead for mapping.
It is possible to concatenate fields and specify a custom pattern with the **FieldsComposite** mapper. You will need to include the following mapper in your config file:
70
-
71
-
```
72
-
{
73
-
"source": "${field1}-${field2}",
74
-
"target": "Custom.TargetField",
75
-
"mapper": "MapFieldsComposite"
76
-
}
77
-
```
78
-
79
-
Here is another example for adding the issue title to the description:
0 commit comments