Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Highest
Fix Version/s: 9.11.0
Affects Version/s: 6.4.0.3, 7.2.6, 9.9.1, 8.20.24, 9.4.8
Component/s: Lexorank
Labels:
- affects-server
- fixme
- flash
- l1l2
- performance
- pse-request

Introduced in Version:
6.04
Support reference count:
66
Symptom Severity:
Severity 3 - Minor
UIS:
161
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:

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

Description

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.

Attachments

Issue Links

causes

JSWSERVER-22000 Lexorank Cleanup Scheduler broken on Oracle databases

Short Term Backlog

JSEV-3253 Loading...

depended on by

JSWSERVER-20910 Remove the ability to have multiple Rank Fields

Gathering Interest

JSWSERVER-20911 Introduce Jira Healthcheck warning to identify multiple Rank fields

Gathering Interest

relates to

JSWSERVER-3723 Support multiple Global Rank Custom Fields

Closed

is blocked by: FLASH-3472 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

was cloned as: RUM-808 Loading...

(1 is blocked by, 19 mentioned in, 1 was cloned as)

Activity

People

Assignee:: Karol Lopacinski

Reporter:: Andriy Yakovlev [Atlassian]

Votes:: 22 Vote for this issue

Watchers:: 29 Start watching this issue

Dates

Created:: 22/Jan/2016 9:35 AM

Updated:: 27/Sep/2023 12:59 PM

Resolved:: 30/Aug/2023 2:48 PM