-
Bug
-
Resolution: Fixed
-
High
-
None
With the transition in JIRA 6 to user keys in lieu of user names, the pre-6.0 issue worklog is not being migrated correctly in the case of users who had LDAP-originating non-lowercase usernames. This results in the worklog entries not being associated with the user.
For example, in the database in JIRA 5.x, the usernames are always stored in lowercase in the database in jiraissue.reporter and jiraissue.assignee. However, in the worklog.author column, the usernames are persisted in mixed case to match the LDAP user.
This works fine in JIRA 5.x because JIRA is performing a case-insensitive match against the username. However, JIRA 6 is once again performing a case-sensitive match, since it apparently assumes that the user keys have all been normalized to lowercase (and so that there is no namespace conflict with the new "IDxxxxx" user keys).
Unfortunately, this assumption fails in the case of the worklog table, since the worklog.author names are still left in mixed case. This yields in a failure to resolve the username when viewing the worklog for those users: it displays just the username (user key) without the display name or the corresponding inline dialog.
- is duplicated by
-
-
- Closed
-
- is cloned from
-
JRADEV-21357 Failed to load
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-66664] Migrated pre-6.0 worklogs with mixed-case usernames are disassociated from authors
Thanks--I didn't read through all 90+ comments, so I hadn't noticed seen that reference.
I see that it was supposed to be fixed in 6.0-m7, but I can confirm that it is still broken in rc1, at least inasmuch as mixed-case usernames are concerned--I don't know about the general case.
On the off chance that it was related to incremental upgrades I did on my dev system through various 6.0 milestone/RC releases, I just re-ran another migration from scratch: I started up a new copy of 6.0-rc1 and fed it a backup from JIRA 5.0 system. The result was the same with mixed-case usernames in the worklogs, so this is not a result of incremental upgrades either.
Bjarni Thorbjornsson
added a comment - FYI: This is already reported on the EAP issue:
https://jira.atlassian.com/browse/JRA-30983?focusedCommentId=441753&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-441753
Bjarni Thorbjornsson
added a comment - FYI: This is already reported on the EAP issue:
https://jira.atlassian.com/browse/JRA-30983?focusedCommentId=441753&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-441753
Apparently, the necessary upgrade task was overlooked. I'm adding it to 6039 and creating 6096 to do just that piece (and careful to preserve any ID12345-style entries) for anyone that has installed 6.0.