resolvedBy is populating from linked issues

This search should return any items:

resolvedBy != "" and status was not in (resolved)

As an item that has never been resolved should not have a resolver. However, linked issues such as "relates to" and "clones" that have been resolved are populating this attribute.

This was noticed when the search: resolvedBy in (user1, user2, user3) and sprint in openSprints()

began returning extra items the given users had not actually touched. This can inflate and give inaccurate figures which need to be rooted out by hand or filtered with something more like:

resolvedBy in (user1, user2, user3) and sprint in openSprints() and assignee was in (user1, user2, user3)

But this is also inaccurate as a true resolver does not necessarily possess the item when resolving.