nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resolved By set to Anonymous or Empty after upgrade

Rob Saunders

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?

Accepted answers

Rob Saunders

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!

All comments

Luther Hargrove

Did you change authentication methods during the upgrade?

Rob Saunders

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

Mizan

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.

Rob Saunders3

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!

Rob Saunders

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!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration