-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
H3. Issue description
Email address is not accepted as a reporter or assignee during the JSON import.
However, Usernames are still allowed to be added as assignee or reporter.
H3. JSON Format used:
{
"projects": [
{
"issues": [
{
"key" : "SF-11223",
"reporter": "ssuvarna@atlassian.com",
"summary": "test import email",
"externalId": "11223"
},
{
"key" : "SF-112234",
"description": "blablabla",
"reporter": "rdey",
"summary": "test import nickname",
"externalId": "112234"
}
],
"key": "SF"
}
]
}
Observed that the issue "SF-11223" is created with a reporter as Anonymous. But the issue "SF-112234" was created with the reporter as rdey (correct user)
H3. How to replicate
- Use the JSON format provided above
- Go to Jira settings --> External System import --> JSON import
H3. Expected results:
Issue "SF-11223" is created with the reporter set to shwetha suvarna(ssuvarna@atlassian.com)
H3. Current Result
Issue "SF-11223" is created with the reporter set to Anonymous
Issue only affects JSON import. CSV import works well with E ail address.
- relates to
-
JRACLOUD-69882 Change CSV import method to map Assignee field to email address
-
- Closed
-