-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
6.4.0.3, 6.4.0.6, 6.4.0.8, 6.4.0.9, 6.4.2, 6.4.3
-
None
-
6.04
-
Symptom:
- When ranking an issue, the following error shown on the browser
- The rank re-balance job is running very slow ie 4 days and no sign of completion.
Cause:
There is a rank value for an issue which is 0|zzzzzr: When this is the last rank value, any new issues created will be assigned a rank which is after the last ranked issue. We generate a new rank value based on the last rank, and in this case the generated rank value equals a special marker rank. This special rank value is not allowed to be inserted, thus preventing the assigning of a rank for new issues.
Diagnosis:
Run the following SQL to identify the special rank marker, if this returns value, then you are affected
select * from "AO_60DB71_LEXORANK" where "RANK" like '%|zzzzzr%';
Workaround:
Update the invalid rank value 0|zzzzzr: to 0|zzzzzr:i using the following SQL
update AO_60DB71_LEXORANK set RANK = '0|zzzzzr:i' where RANK like '%|zzzzzr%';
- is cloned from
-
JSWSERVER-10872 Unable to rank issues in JIRA Agile
- Closed
- is duplicated by
-
JSWSERVER-10873 Slow / not working due to errors with gh.lexorank.service.error.retrytimeout
- Closed
-
JSWSERVER-11358 LexoRank integrity is breached by values set outside the markers
- Closed
- is related to
-
JSWSERVER-10881 Can not reorder tickets in current sprint, asks to re-index (does not fix)
- Closed
-
JSWSERVER-10880 JIRA Agile cannot execute the rank operation
- Closed
-
JSWSERVER-10892 lexorank value problem
- Closed
-
JSWSERVER-10890 Harden rendering of issues in epic panel when issues don't have a rank value
- Closed
- relates to
-
JSWSERVER-10868 Ranking on scrum board has broken for new issues
- Closed
-
JSWSERVER-10910 Use of ROWNUM in Oracle select statement incorrect
- Closed
-
JSWSERVER-11050 Unable to rank New issues
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...