Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11044

Unable to rank issues in JIRA Agile 6.4.3 due to invalid marker rank

XMLWordPrintable

      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%';

        1. epic.png
          epic.png
          27 kB
        2. jira_log_whenCreatingNewIssue.txt
          27 kB
        3. JST-105908_jira.lexorank.csv
          180 kB
        4. JST-105922_jira.lexorank.csv
          167 kB

            [JSWSERVER-11044] Unable to rank issues in JIRA Agile 6.4.3 due to invalid marker rank

            MichaelA (Inactive) added a comment -

            Looking at the logs, you are running in a corner case problem; 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.

            The temporary solution is to change this corner case rank value to alleviate in the short term. You can change the rank value to 0|zzzzzr:i for example.

            We already fixed this and it will be released in JAG 6.4.5

            MichaelA (Inactive) added a comment - Looking at the logs, you are running in a corner case problem; 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. The temporary solution is to change this corner case rank value to alleviate in the short term. You can change the rank value to 0|zzzzzr:i for example. We already fixed this and it will be released in JAG 6.4.5

            Honeywell JIRA Admin added a comment -

            We are facing this issue JIRA 6.4.3 as well.The Rank re-balance is running for 4 days and still continuing.

            Honeywell JIRA Admin added a comment - We are facing this issue JIRA 6.4.3 as well.The Rank re-balance is running for 4 days and still continuing.

              Unassigned Unassigned
              ad9744759bcd Honeywell JIRA Admin
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: