If Sprint field is misconfigured then reindex of issues will blow up

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Highest
    • 5.9.7.1
    • Affects Version/s: 5.9.7
    • Component/s: None
    • 5.09

      The two cases which are considered "misconfiguration":

      • The Sprint field is not a Global custom field (i.e. it is not mapped to all projects and all issue types)
      • The Sprint field is Hidden in some Field Configuration Scheme

      You will see this in the logs:

      Caused by: java.lang.IllegalArgumentException: it doesn't make sense to have a field that is neither indexed nor stored
at org.apache.lucene.document.Field.<init>(Field.java:400)
at org.apache.lucene.document.Field.<init>(Field.java:371)
at org.apache.lucene.document.Field.<init>(Field.java:350)
at com.atlassian.greenhopper.customfield.sprint.SprintCustomFieldIndexer.addDocumentFields(SprintCustomFieldIndexer.java:61)
at com.atlassian.greenhopper.customfield.sprint.SprintCustomFieldIndexer.addDocumentFieldsNotSearchable(SprintCustomFieldIndexer.java:34)
at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(AbstractCustomFieldIndexer.java:50)
      Workaround

      The following KB article has been written up as a work around to this issue please go here to view it Indexing error: It doesn't make sense to have a field that is neither indexed nor stored
      It is recommended to upgrade GreenHopper off 5.9.7 and then follow the guide in the KB to ensure that the rapid boards are showing.

            Assignee:
            Unassigned
            Reporter:
            Michael Tokar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: