Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-7300

Allow custom fields to show values in Issue Navigator based on the Lucene document

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently the Document version of an issue (JRA-6874) is limited to system fields, and is badly hard-coded. We need to introduce a new interface for fields that can load their values from the document, and use that instead.

      We can then allow custom fields to load their own values from the document. This would improve performance in the issue navigator significantly when large numbers of custom fields are displayed (from my calculations - it would roughly halve the time to display the table).

            [JRASERVER-7300] Allow custom fields to show values in Issue Navigator based on the Lucene document

            ɹǝʞɐq pɐɹq added a comment -

            done for all intents and purposes

            ɹǝʞɐq pɐɹq added a comment - done for all intents and purposes

            ɹǝʞɐq pɐɹq added a comment -

            And update on this old improvement request

            We currently load all of the JIRA provided custom fields from index. By as Brenden point out to me

            ...CustomFieldType decides if we read from the index or NOT. All our CFT implementations read from the DB. Plugins can kinda do what they want but they would really have to read from the DB since we don't give them access to the index. The CFT.getValueFromIssue method is generic as it is used from the view issue page and does not have enough information to make the decision to read from the index or the database.

            So in some sense this issue could be considered closed. However if we include the requirement that plugin CF can read from the index then its not done.

            I am inclined to close this issue.

            ɹǝʞɐq pɐɹq added a comment - And update on this old improvement request We currently load all of the JIRA provided custom fields from index. By as Brenden point out to me ...CustomFieldType decides if we read from the index or NOT. All our CFT implementations read from the DB. Plugins can kinda do what they want but they would really have to read from the DB since we don't give them access to the index. The CFT.getValueFromIssue method is generic as it is used from the view issue page and does not have enough information to make the decision to read from the index or the database. So in some sense this issue could be considered closed. However if we include the requirement that plugin CF can read from the index then its not done. I am inclined to close this issue.

              Unassigned Unassigned
              scott@atlassian.com Scott Farquhar
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: