Our use case is unifying the user naming convention after historically different nameing schemes. This open issue blocks us from doing so. We will look into a solution on API- or database-level. If anyone has done this before, feel free to put it in the comments and @-mention me.

I have just open a support case (GHS-195041) for a similar issue related to having to change user names to match up with a SAML auth provider who users email address as the identifier. As email addresses tend to be more unique than a username, would Atlassian concider using email address as the filter "assignee" identifier that gets added when the user lookup fills in the value rather than using the username?

FWIW this also applies to the Agile Board Quick Filters.

Sadly the Quick Filters are not accessible via REST API. So AFAIK you can't even write a script to update the filters

hernandez.oswaldo this may well now be obsolete as I couldn't reproduce the issue in JIRA 7.0.9 as I could with 6.x. The problem appears to have caused JSD-3318, which is only reproducible in 6.x versions as well.

Hi.

I renamed a user and had now the problem, that his filters have not been migrated (searchrequest.authorname was the old name).
The I updated the database table and set the author to the new username.

Then I cleared Jira and groovy caches and did a reindex.
The user can't see his filters (and dashboards).

I now saw the the app_user table holds User_key with bank and the lowerusername without blank.
Do I have to change the user_key as well?

Thanks a lot,
Petra

Hi dleng,

I have just had a chat with mlassau about this issue and it turns out that this is a known limitation in the user rename functionality. I will move this to an Improvement request accordingly.

Cheers,
Os.

Some considerations:

1. Is the Lucene indexes taking stuff from cwd_user table or app_user table ? As far as I know, the app_user table stores the original username for backward compatibility. But Im not sure if Lucene works on that table.