-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Backup & Restore - Import From JIRA Server
-
None
-
1
-
Minor
Issue Summary
Assignee was JQL does not work for usernames with capital letters
Steps to Reproduce
1. Import data from server to cloud. Include a user with capital letters in the username (ie. User.Sample)
| select au.user_key, au.lower_user_name, cu.user_name, cu.email_address, cu.external_id from app_user au join cwd_user cu on au.lower_user_name = cu.lower_user_name and cu.email_address = 'user.ramon@atlasbean.com' |
| user_key | lower_user_name | user_name | email_address | external_id |
|---|---|---|---|---|
| user.sample | user.sample | User.Sample | user.sample@atlasbean.com | 5f73302458899e00704f4374 |
2. Import a Jira issue via JSON and assign to the accountID of the user with capital letters on the username.
{"projects": [{
"name": "SCRUM TESTING",
"issues": [
{
"summary": "TEST SUMMARY",
"creator": "5f73302458899e00704f4374",
"created": "2020-03-12T09:23:36.897+0000",
"reporter": "5f73302458899e00704f4374",
"assignee": "5f73302458899e00704f4374",
"issueType": "Story",
"key": "ST-114",
"externalId": "Ext-ST-114",
"status": "To Do"
}
],
"key": "ST"
}]}
3. Do a JQL Search:
assignee was <ACCOUNTID>
Expected Results
The Jira issue where the imported user is assigned should be returned.
Actual Results
The Jira issue where the imported user is assigned is not returned.
- assignee was <ACCOUNTID> does not work
- assignee = <ACCOUNTID> works.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...