-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
6.5.0, 6.6.0
-
None
-
6.05
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
New issues can't be ranked. The error message displayed is:
in red or in yellow message.
JIRA Agile cannot execute the rank operation. This board has recently been configured to use the Rank field. The system must be re-indexed before you can rank issues. Ask your administrator to perform a manual re-index.
Cause:
When new issues are created, JIRA Agile fails to assign a new Rank value to issues.
To verify:
Do an issues search <JIRA-BASE-URL>/issues/?jql=order%20by%20created%20desc and add Rank as a column to the list. New issues won't display a Rank value.
If they now do, then they will be able to be ranked now.
Workaround: (on OnDemand create a support request at http://support.atlassian.com )
- run a rebalance with sysadmin user going to <JIRA-BASE-URL>/rest/greenhopper/1.0/lexorank/balance
- run a Background reindex.
Notes:
This query can be used in the database to find what issues don't have a Rank:
select p.pkey, j.issuenum, p.pname from jiraissue j left join project p on p.id = j.project where j.id not in (select "ISSUE_ID" from "AO_60DB71_LEXORANK") order by p.pkey, j.issuenum;
- is related to
-
JSWSERVER-11044 Unable to rank issues in JIRA Agile 6.4.3 due to invalid marker rank
- Closed
- relates to
-
JSWCLOUD-11050 Unable to rank New issues
- Closed
-
JSWSERVER-10872 Unable to rank issues in JIRA Agile
- Closed
-
JSWSERVER-20691 Lexorank affects issue creation time
- Long Term Backlog
-
SW-595 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...