-
Suggestion
-
Resolution: Fixed
-
None
Currently for displaying parts of the issue table, many database queries are made. The following fields need database calls:
- parent issue (summary field)
- sub-tasks
- components
- fix versions
- affected versions
We should create an issue implementation that is based on a document, (which has those fields normalised) for a performance increase.
- details
-
JRASERVER-6892 Restore sorting in users votes & watches page
- Closed
-
JRASERVER-6901 Create linked issues system field
- Closed
-
JRASERVER-6890 Sort the columns in navigator-excel-full correctly, and show full headings
- Closed
- is related to
-
JRASERVER-7300 Allow custom fields to show values in Issue Navigator based on the Lucene document
- Closed
- relates to
-
JRASERVER-6816 Change the Issue interface to be MutableIssue, and Issue
- Closed