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

JIRA Agile doesn't delete rank from table when the Custom Field was deleted

XMLWordPrintable

    • 6.04
    • 66
    • Severity 3 - Minor
    • 161
    • Hide
      Atlassian Update – 07 July 2023

      Thank you for reporting this issue. In the last weeks we have been working hard on fixing it.

      Summary of the problem:

      JIRA Agile doesn't delete rank data from AO_60DB71_LEXORANK table when the Custom Field was deleted

      New behaviour after the change:

      A background job looks for orphaned records in the AO_60DB71_LEXORANK database table that no longer have corresponding Custom Fields and deletes them. This happens once every 30 minutes by default.

      Status of the fix and Fix Version:

      The fix is ready, and we’re moving the status of this ticket to Waiting for release with Fix Version 9.11.0.

      Regards,
      Karol Lopacinski
      Senior Software Engineer

      Show
      Atlassian Update – 07 July 2023 Thank you for reporting this issue. In the last weeks we have been working hard on fixing it. Summary of the problem: JIRA Agile doesn't delete rank data from  AO_60DB71_LEXORANK  table when the Custom Field was deleted New behaviour after the change: A background job looks for orphaned records in the AO_60DB71_LEXORANK database table that no longer have corresponding Custom Fields and deletes them. This happens once every 30 minutes by default. Status of the fix and Fix Version: The fix is ready, and we’re moving the status of this ticket to Waiting for release with Fix Version 9.11.0. Regards, Karol Lopacinski Senior Software Engineer

      Summary

      JIRA Agile doesn't delete rank data from AO_60DB71_LEXORANK table when the Custom Field was deleted

      Steps to Reproduce

      1. Follow KB Remove+Duplicate+LexoRank and delete duplicated Agile Rank data.
      2. Check AO_60DB71_LEXORANK table 
        select "FIELD_ID",count("FIELD_ID") from "AO_60DB71_LEXORANK" group by "FIELD_ID";
      3. Check AO_60DB71_LEXORANKBALANCER table 
        select "FIELD_ID" from "AO_60DB71_LEXORANKBALANCER";

      Expected Results

      Data with single FIELD_ID 

      select "FIELD_ID",count("FIELD_ID") from "AO_60DB71_LEXORANK" group by "FIELD_ID";
     15200	      854577

select "FIELD_ID" from "AO_60DB71_LEXORANKBALANCER";
     15200

      Actual Results

      Data with multiple FIELD_ID:

      select "FIELD_ID",count("FIELD_ID") from "AO_60DB71_LEXORANK" group by "FIELD_ID";
     15200	      854577
     15201	      822690

select "FIELD_ID" from "AO_60DB71_LEXORANKBALANCER";
     15200
     15201

      Notes

      Potentially fixed in JIRA Software 7.0.4.
      To check current Agile custom fields:

      // List Agile customfields
select * from customfield where customfieldtypekey like 'com.pyxis.greenhopper.jira%';

// Default lexorank field
SELECT propertyvalue FROM propertyentry LEFT JOIN propertynumber ON propertyentry.ID = propertynumber.ID WHERE property_key = 'GreenHopper.LexoRank.Default.customfield.id';

      Workaround

      Stop JIRA and delete data manually.

              klopacinski Karol Lopacinski
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              22 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: