Indexing issues

There are certain cases, where your issue index might not work correctly.

Outlook Email for Jira & Microsoft 365 for Jira are both installed

If you have both apps installed on Jira Server, indexing will not work correctly. If you have both installed, we recommend uninstalling Outlook Email for Jira, because all of the functionality is already included in the Microsoft 365 app. The following error indicates this:

CODE

DocValuesField "ISSUEPROP_yasoon-outlook-email-data$id" appears more than once in this document (only one value is allowed per field)

Migration from Jira Cloud → Jira Server

If your Jira Server system was migrated from a Jira Cloud instance, you might get the following error:

DocValuesField "ISSUEPROP_yasoon-outlook-email-data$involvedEmailAddresses" appears more than once in this document (only one value is allowed per field)

This basically means, that some issues were created from Outlook and contain issue properties that are not compatible with the Jira index we use on Jira Server. To fix this, you can remove the existing issue properties - you’ll lose the connection between the email and the Jira issue though.

Also, before executing DELETE statements on your database, please make sure you have a (working) backup.

SQL

-- Remove all entries from DB with index property key "yasoon-outlook-email-data"
-- e.g. for PostgreSQL
DELETE FROM entity_property WHERE property_key = 'yasoon-outlook-email-data'

Please get in touch in case you’d prefer an alternative solution, we are currently evaluating if the move from Cloud to Server is something we’d need to support in an official manner.