-
Suggestion
-
Resolution: Cannot Reproduce
-
0
-
11
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
When you rename a user's username, all existing filters that still use the old username should still be working fine. This doesn't seem to be the case.
Take an example here: we renamed "johndoe" to "johndoe2345", opening an existing filter that still has:
assignee = "johndoe"
Would not show any error at first, it just says "no issues found". But refreshing the page would say: "The value 'johndoe' does not exist for the field 'assignee'." In fact, johndoe actually has issues assigned to him.
Reindexing doesn't fix the issue.
WORKAROUND:
Manually edit the JQL filter to reflect the new username.
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
[JRACLOUD-36971] Renamed users break existing 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:
- 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.
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