<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=299788&amp;fmt=gif">

LexoRank Negative Field_ID

Atlassian, Jira

Guest Contributor: Jason Wilcox

While troubleshooting ranking error messages showing within the Jira UI, a colleague and I came across approximately 1,800 FIELD_IDs within the LexoRank table having a negative integer out to 15 places. These immediately looked out of place considering every other FIELD_ID within the table carried a positive integer and wasn't nearly as lengthy. We hypothesized that these were possibly corrupted entries or orphaned fields, perhaps removed from within the UI but never successfully removed from the LexoRank table.

Upon working with Atlassian Support in this regard, they explained that the 15 place negative integer values as FIELD_IDs within the table were entries from the Portfolio for Jira app. I've provided a screenshot showing the inserted rows:

Old Jira LexoRank

For posterity I've provided a screenshot of a barebones version of the LexoRank table so you can see what a typical Jira Software FIELD_ID might look like. You'll notice the FIELD_ID is of type (bigint). Signed fifteen digit integers may be allowed. Still, the other technician and I didn't fully understand why these particular FIELD_IDs deviated to such a large degree from our basic Jira Software FIELD_ID, like '10105' for example. As we began troubleshooting, neither of us considered that one of the apps had the potential to use the table. Since I'm sure I'll be looking into LexoRank workings in the future, it's nice to dispel some of the mystery around this bit of information. I hope it proves useful to others should they run across LexoRank issues and assume these are the culprit rows.

Still, this information was advantageous to us. One of our migration project requirements was to remove the Portfolio for Jira app. Knowing for certain Jira would no longer need to reference these FIELD_IDs in the new environment, we were able to remove these values confidently and permanently using our migration scripts, resulting in a cleaner migration environment and potentially a better ranking experience for the end user.

New Jira LexoRank

 If you have familiarity with the LexoRank table, perhaps other plugins writing information to the LexoRank table or if this article helped you in some way, please leave a comment.

Managing JIRA at Scale White Paper

TAGS: Atlassian, Jira

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Subscribe to Our Newsletter

Recent Blog Posts