-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Problem Definition
Until JSWSERVER-20910 is introduced, our customers could use a healthcheck warning thrown when there are more than one Rank field in the instance.
Third-party tools can import multiple Rank fields which can have havoc over indexing performance. Introduction of a new rank field might go unnoticed by administrators as this is not a visible field on the issue view. So administrators might not be aware of this newly introduced Rank field until it's too late.
Suggested Solution
A Jira healthcheck warning can proactively let the admins know that they have multiple Rank fields and this can potentially impact indexing performance.
A "Fix" button should check if the non-default Rank field(s) is/are being used in any of the filters and if not delete the Rank field.
Workaround
Manually check if there are more than 1 Rank field in the Lexorank Management page on the Jira UI (esp. after a project import) and if you see more than one Rank field, follow this kb to Manually Remove duplicate Rank fields in Jira server
Keep in mind deleting the Rank field doesn't delete the Rank data from the AO_60DB71_LEXORANK table. Ref: JSWSERVER-13098: JIRA Agile doesn't delete rank from table when the Custom Field was deleted
- depends on
-
JSWSERVER-13098 JIRA Agile doesn't delete rank from table when the Custom Field was deleted
-
- Closed
-
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[JSWSERVER-20911] Introduce Jira Healthcheck warning to identify multiple Rank fields
| UIS | Original: 1 | New: 0 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 769119 ] |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Link |
New:
This issue depends on |
| Description |
Original:
h3. Problem Definition
Until [JSWSERVER-20910|https://jira.atlassian.com/browse/JSWSERVER-20910] is introduced, our customers could use a healthcheck warning thrown when there are more than one Rank field in the instance. Third-party tools can import multiple Rank fields which can have havoc over indexing performance. Introduction of a new rank field might go unnoticed by administrators as this is not a visible field on the issue view. So administrators might not be aware of this newly introduced Rank field until it's _too late_. h3. Suggested Solution A Jira healthcheck warning can proactively let the admins know that they have multiple Rank fields and this can potentially impact indexing performance. h3. Workaround Manually check if there are more than 1 Rank field in the [Lexorank Management page |https://confluence.atlassian.com/adminjiraserver/managing-lexorank-938847803.html] on the Jira UI (_esp. after a project import_) and if you see more than one Rank field, follow this kb to [Manually Remove duplicate Rank fields in Jira server|https://confluence.atlassian.com/jirakb/remove-duplicate-rank-fields-in-jira-server-779159223.html] |
New:
h3. Problem Definition
Until [JSWSERVER-20910|https://jira.atlassian.com/browse/JSWSERVER-20910] is introduced, our customers could use a healthcheck warning thrown when there are more than one Rank field in the instance. Third-party tools can import multiple Rank fields which can have havoc over indexing performance. Introduction of a new rank field might go unnoticed by administrators as this is not a visible field on the issue view. So administrators might not be aware of this newly introduced Rank field until it's _too late_. h3. Suggested Solution A Jira healthcheck warning can proactively let the admins know that they have multiple Rank fields and this can potentially impact indexing performance. A "Fix" button should check if the non-default Rank field(s) is/are being used in any of the filters and if not delete the Rank field. h3. Workaround Manually check if there are more than 1 Rank field in the [Lexorank Management page |https://confluence.atlassian.com/adminjiraserver/managing-lexorank-938847803.html] on the Jira UI (_esp. after a project import_) and if you see more than one Rank field, follow this kb to [Manually Remove duplicate Rank fields in Jira server|https://confluence.atlassian.com/jirakb/remove-duplicate-rank-fields-in-jira-server-779159223.html] (!) Keep in mind deleting the Rank field doesn't delete the Rank data from the *AO_60DB71_LEXORANK* table. Ref: [ |
| Description |
Original:
Until [JSWSERVER-20910|https://jira.atlassian.com/browse/JSWSERVER-20910] is introduced, our customers could use a healthcheck warning thrown when there are more than one Rank field in the instance.
Third-party tools can import multiple Rank fields which can have havoc over indexing performance. Introduction of a new rank field might go unnoticed by administrators as this is not a visible field on the issue view. So administrators might not be aware of this newly introduced Rank field until it's _too late_. A Jira healthcheck warning can proactively let the admins know that they have multiple Rank fields and this can potentially impact indexing performance. |
New:
h3. Problem Definition
Until [JSWSERVER-20910|https://jira.atlassian.com/browse/JSWSERVER-20910] is introduced, our customers could use a healthcheck warning thrown when there are more than one Rank field in the instance. Third-party tools can import multiple Rank fields which can have havoc over indexing performance. Introduction of a new rank field might go unnoticed by administrators as this is not a visible field on the issue view. So administrators might not be aware of this newly introduced Rank field until it's _too late_. h3. Suggested Solution A Jira healthcheck warning can proactively let the admins know that they have multiple Rank fields and this can potentially impact indexing performance. h3. Workaround Manually check if there are more than 1 Rank field in the [Lexorank Management page |https://confluence.atlassian.com/adminjiraserver/managing-lexorank-938847803.html] on the Jira UI (_esp. after a project import_) and if you see more than one Rank field, follow this kb to [Manually Remove duplicate Rank fields in Jira server|https://confluence.atlassian.com/jirakb/remove-duplicate-rank-fields-in-jira-server-779159223.html] |
| Labels | Original: pse-request | New: clean-up performance pse-request |
| Labels | New: pse-request |