Resolved By set to Anonymous or Empty after upgrade

We just upgraded our JIRA from 5.1 to 6.2 and it was a pretty smooth process (fantastic!)

It now seems as though every issue in our system has the 'Resolved BY' field set to 'Anonymous'.

In JQL all issues in our system will be returned by the following:

Resolved BY = EMPTY

We've re-indexed.

Any ideas?

5 answers

1 accepted

0 votes
Accepted answer

Thanks for the suggestions guys, the issue ended up relating to the Enhancer plugin / add-on.

This add-on was updated when we upgraded our JIRA version, but the updated version (3.0 snapshot if I remember correctly) was not the latest version.

Once we uninstalled this plugin and re-purchased it from the marketplace, the new version (4.3.8) worked as it used to, and all of our old data was visible as it was in the past.

This is my fault for not identifying the 'Resolved By' field as relating to this plugin much earlier!

Did you change authentication methods during the upgrade?

We didn't intentionally change any authentication methods.

How might authentication change this field?

We currently use the JIRA Internal Directory for user authentication

If I create a new issue, pass it through the normal stages of our existing workflow until it is closed, the Resolved By field is set to Anonymous

I guess you are using a post functions to set the value of this field? Check the logs what it says when you resolve an issue . Also check the postfunctions on the resolve transitions.

Thanks for the suggestions guys, the issue ended up relating to the Enhancer plugin / add-on.

This add-on was updated when we upgraded our JIRA version, but the updated version (3.0 snapshot if I remember correctly) was not the latest version.

Once we uninstalled this plugin and re-purchased it from the marketplace, the new version (4.3.8) worked as it used to, and all of our old data was visible as it was in the past.

This is my fault for not identifying the 'Resolved By' field as relating to this plugin much earlier!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,770 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you