-
Type:
Bug
-
Status: Gathering Impact (View Workflow)
-
Priority:
Low
-
Resolution: Unresolved
-
Affects Version/s: 6.4.0.3, 7.2.6
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Introduced in Version:6.04
-
Support reference count:32
-
Symptom Severity:Severity 3 - Minor
-
UIS:48
-
Bug Fix Policy:
Summary
JIRA Agile doesn't delete rank data from AO_60DB71_LEXORANK table when the Custom Field was deleted
Steps to Reproduce
- Follow KB Remove+Duplicate+LexoRank and delete duplicated Agile Rank data.
- Check AO_60DB71_LEXORANK table
select "FIELD_ID",count("FIELD_ID") from "AO_60DB71_LEXORANK" group by "FIELD_ID";
- 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.