Sometime in the past, our administrators turned "allow unassigned issues" off. Time passed, but the people clamored for unassigned issues. In their short-sightedness, new administrators, instead of turning the setting back on, created an "Unassigned" user (with the username "unassigned").
Fast-forward and the Unassigned user has 1000s of issues assigned. A benevolent administrator is trying to return to allowing properly unassigned tickets. I was able to bulk edit and change the assignment. But, the Unassigned user's "username" is the same as the special username for tickets that are properly unassigned.
I cannot remove the Unassigned user because it appears, to JIRA, to perpetually have tickets assigned to it!
----
For anyone else dealing with the same:
I marked the Unassigned user "inactive" so it couldn't be assigned. I changed it's name to "nobody", which helped to see (in some searches) that it really wasn't used. I changed all projects where it was the default-assigned Project Lead to use unassigned properly.
Hello Anthony,
After running this bulk change, did you have the chance to run a full locked re-index?
https://confluence.atlassian.com/display/JIRA/Re-Indexing+after+Major+Configuration+Changes
Please run this and let us know if the indexing of the issues bulk-changed appears correct.
Hi Anthony,
Thanks for sharing this experience with us. Indeed a user cannot be removed when it still has issues created on his username, so it's possible that there is, still something locking it.
I suggest you to check on your database for this user (nobody) and see where it is still set, specially on the tables related to issues such as jiraissue.
Here is the Jira Database Schema:
https://developer.atlassian.com/display/JIRADEV/Database+Schema#DatabaseSchema-IssueFields
PS: Instead of checking each table, creating a database dump and then analyzing it as text, should help on looking for this user in all tables at once.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm certain that the user has no more tickets assigned. I bulk changed 1000s of tickets today. The fake-unassigned user's profile still shows all of these tickets! I just assigned a new ticket to the built-in unassigned and this fake-unassigned user's ticket count increased!
The problem seems to be in the username (field) or the assignee (search field). It's literally "unassigned" for both my user and the built-in user that JIRA uses for unassigned tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.