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

          Form Name

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

            J. Sakurai made changes -
            Link New: This issue was cloned as JSWSERVER-20401 [ JSWSERVER-20401 ]
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.04
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2854986 ] New: JAC Bug Workflow v3 [ 2933209 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2541962 ] New: JAC Bug Workflow v2 [ 2854986 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549188 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2541962 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: HOT-9464 OnDemand fixme ondemand-support-workaround New: HOT-9464 OnDemand affects-server fixme ondemand-support-workaround
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908583 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549188 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747407 ] New: JIRA Bug Workflow w Kanban v6 [ 908583 ]
            Jaime S made changes -
            Description Original: h4.Symptom:

            * When ranking an issue, the following error shown on the browser
            !epic.png|thumbnail!
            * The rank re-balance job is running very slow ie 4 days and no sign of completion.

            h4.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.

            h4.Diagnosis:

            Run the following SQL to identify the special rank marker, if this returns value, then you are affected
            {code:sql}
            select * from AO_60DB71_LEXORANK where RANK like '%|zzzzzr%';
            {code}

            h4.Workaround:

            Update the invalid rank value 0|zzzzzr: to 0|zzzzzr:i using the following SQL
            {code:sql}
            update AO_60DB71_LEXORANK set RANK = '0|zzzzzr:i' where RANK like '%|zzzzzr%';
            {code}             		New: h4.Symptom:

            * When ranking an issue, the following error shown on the browser
            !epic.png|thumbnail!
            * The rank re-balance job is running very slow ie 4 days and no sign of completion.

            h4.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.

            h4.Diagnosis:

            Run the following SQL to identify the special rank marker, if this returns value, then you are affected
            {code:sql}
            select * from "AO_60DB71_LEXORANK" where "RANK" like '%|zzzzzr%';
            {code}

            h4.Workaround:

            Update the invalid rank value 0|zzzzzr: to 0|zzzzzr:i using the following SQL
            {code:sql}
            update AO_60DB71_LEXORANK set RANK = '0|zzzzzr:i' where RANK like '%|zzzzzr%';
            {code}
            Kiran (Inactive) made changes -
            Link New: This issue is duplicated by GHS-11358 [ GHS-11358 ]

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

                Created:
                Updated:
                Resolved: