Issue Summary
When a custom field is deleted entries from AO_8542F1_IFJ_OBJ_JIRAISSUE table are not removed, leaving a big amount of orphaned data.
Steps to Reproduce
- I created an Assets custom field. Created new issue and populated the field
- new entry created on AO_8542F1_IFJ_OBJ_JIRAISSUE
- I deleted the field
- the entry remains on AO_8542F1_IFJ_OBJ_JIRAISSUE
- however AO_8542F1_IFJ_DCF_CONNECT was cleared
- I deleted the Issue
- the entry was removed from AO_8542F1_IFJ_OBJ_JIRAISSUE
- Created another Assets custom field. Created a new Issue and populated the field
- new entry created on AO_8542F1_IFJ_OBJ_JIRAISSUE
- I Edit the Issue and left the Assets custom field empty
- the entry was removed from AO_8542F1_IFJ_OBJ_JIRAISSUE
Expected Results
When the custom field is deleted the entry on AO_8542F1_IFJ_OBJ_JIRAISSUE table is removed (this is what happens when the value on the custom field is empty).
Actual Results
Nothing changes on the AO_8542F1_IFJ_OBJ_JIRAISSUE table, and even if the association does not exist anymore, there's an entry indicating the issue has a custom field, which does not exist anymore.
Workaround
The data needs to be manually deleted from AO_8542F1_IFJ_OBJ_JIRAISSUE table.
Versions Tested
Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below:
| Testing Requirements |
Version |
Affected Version |
| Customers Reported Version |
5.12.15 |
yes |
| Most Recent Bug-Fix Release |
10.6.0 |
yes |
| Previous Major Release |
|
|
| Most Recent LTS |
|
|
| Previous Supported LTS |
|
|
| Other Versions.. |
10.3.1 |
yes |
| (Add rows as needed) |
|
|
Bug
Low
