-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
28
-
Minor
-
0
-
Issue Summary
LexoRank Balancing may stop working erroneously which can cause issues with certain operations. Known issues at the moment are:
- Issue Move
- Rank issues
- Create an Advanced Roadmap plan
- Export to CSV
More will be added as we come across.
Thus we need to find a way to never break lexorank integrity.
Steps to Reproduce
N/A.
Expected Results
- All operations like issue transition, move, ranking, etc should work fine without throwing any lexorank related errors.
- Show a descriptive error message explaining operation is failed due to Lexorank issue instead of “500 - Internal server error" OR
- Provide the ability for users to recover from LexoRank issues.
Actual Results
The below exception is thrown on UI:
Error type: 500 - Internal server error
Workaround:
Contact the support team via support.atlassian.com.
- is related to
-
JRACLOUD-86911 Error when ranking issues due to lexorank data integrity problem
-
- Closed
-
- relates to
-
MIG-915 Importing to Cloud using JCMA is duplicating issue ranks
-
- Closed
-
- was split into
-
JRACLOUD-90946 LexoRank - Duplication in Ranking
-
- Closed
-
-
JRACLOUD-90962 LexoRank - Issues in the Wrong Bucket
-
- Closed
-
-
JRACLOUD-90937 LexoRank - Cannot rank issues
-
- Closed
-
-
JRACLOUD-90950 LexoRank - Issues without rank association
-
- Closed
-
- causes
-
ISSUE-4068 Loading...
-
ISSUE-4069 Loading...