-
Bug
-
Resolution: Duplicate
-
High (View bug fix roadmap)
-
None
-
6.4.0.9
-
6.04
-
Our Jira has the following problems
- create / edit tasks is slow
- move tasks does not work for some users.
In the log I only see the following:
2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10201] and issue [12604] 2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankCFType] gh.lexorank.service.error.retrytimeout 2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankIndexer] Could not retrieve LexoRank value for issue[id=12604]. Indexing max LexoRank value instead.
I see that there was some similar bugs in 6.4.0.6-7, but they should be fixed in 6.4.0.8 and 6.4.0.9.
- duplicates
-
JSWSERVER-10872 Unable to rank issues in JIRA Agile
-
- Closed
-
-
JSWSERVER-11044 Unable to rank issues in JIRA Agile 6.4.3 due to invalid marker rank
-
- Closed
-
- relates to
-
JSWSERVER-20691 Lexorank affects issue creation time
-
- Closed
-
Form Name |
---|
[JSWSERVER-10873] Slow / not working due to errors with gh.lexorank.service.error.retrytimeout
Link |
New:
This issue relates to |
Minimum Version | New: 6.04 |
Workflow | Original: JAC Bug Workflow v2 [ 2852032 ] | New: JAC Bug Workflow v3 [ 2934822 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545951 ] | New: JAC Bug Workflow v2 [ 2852032 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551737 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545951 ] |
Assignee | Original: Renan Battaglin [ rbattaglin ] |
Assignee | New: Renan Battaglin [ rbattaglin ] |
Labels | Original: fixme warranty | New: affects-server fixme warranty |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 909869 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551737 ] |
agreed with @andreas.schoen:
It seems that minimum process on jira-6.2.3 with postgresql db is to backup data, create new database with C collation and then restore data.