Is there a fix for the issue where the component watcher plugin is picking up deleted and disabled users?

[Leila Pearson]

We have run into a case, for at least a couple of users, where they cannot be assigned as component watchers.  What appears to be happening is:

• We had some local use account - e.g. johndoe - a while back.
• We changed the name of that account to johndoe-local
• We attached to an LDAP directory, which brought in a johndoe account

The problem is, even though we specify "johndoe" as a watcher, we get "johndoe-local".  It seems as if the lookup is based on the old name of the user, not the new account name.

We tried disabling the johndoe-local account.  It still is the one that gets added as a watcher - even though it doesn't exist.

We tried deleting the johndoe-local account.  It still is the one that gets added as a watcher - even though it doesn't exist.

It isn't practical to change the name of the LDAP account since this is the corporate account for the user, used everywhere, and following corporate naming standard.

Someone from Atlassian was already kind enough to take a look a the problem, and it seems to be a plugin bug.  See https://bitbucket.org/rbarham/jira-component-watcher-plugin/issue/15/not-handling-renamed-and-deleted-users

Can you help?

[Leila Pearson]

Thanks Daniel.  There was no response from the developer on that one, so I was hoping this avenue might work better since this is the link provided on the Marketplace for supporting this plugin.  

[Daniel Wester]

Looks like there's an open issue for it at https://bitbucket.org/rbarham/jira-component-watcher-plugin/issue/15/not-handling-renamed-and-deleted-users