-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.0.0, 4.0.0, 5.0.0, 5.17.2
-
1
-
Severity 3 - Minor
-
0
-
Problem
Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types.
Suggested Solution
When removing a custom field that is not in use anymore, any reference to it should also be removed from the database
Why This Is Important
Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:
2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request] Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support' com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'
Workaround
- A possible workaround is to manually delete the records from the "AO_54307E_VIEWPORTFIELD" table. However, please be careful when doing so, as that table holds data related to all custom fields in use by any Request Type. You can find the detailed steps on how to do that in the KB article https://confluence.atlassian.com/jirakb/error-occurs-on-deleted-customfield-when-migrating-jira-projects-by-using-project-configurator-for-jira-1360661228.html
- Other than that, another approach would be to actually reach out to the third-party app developer for assistance on how to proceed with those errors.
- links to
[JSDSERVER-15464] Deleting custom fields used in Request types leaves information in the Jira database that should be removed
| UIS | Original: 1 | New: 0 |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 956109 ] |
| UIS | New: 1 |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Problem
Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types. h3. Suggested Solution _When removing a custom field that is not in use anymore, any reference to it should also be removed from the database_ h3. Why This Is Important _Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:_ {code}2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request] Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support' com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'{code} h3. Workaround * A possible workaround is to manually delete the records from the "AO_54307E_VIEWPORTFIELD" table. However, please be careful when doing so, as that table holds data related to all custom fields in use by any Request Type. * Other than that, another approach would be to actually reach out to the third-party app developer for assistance on how to proceed with those errors. |
New:
h3. Problem
Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types. h3. Suggested Solution _When removing a custom field that is not in use anymore, any reference to it should also be removed from the database_ h3. Why This Is Important _Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:_ {code}2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request] Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support' com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'{code} h3. Workaround * A possible workaround is to manually delete the records from the "AO_54307E_VIEWPORTFIELD" table. However, please be careful when doing so, as that table holds data related to all custom fields in use by any Request Type. You can find the detailed steps on how to do that in the KB article https://confluence.atlassian.com/jirakb/error-occurs-on-deleted-customfield-when-migrating-jira-projects-by-using-project-configurator-for-jira-1360661228.html * Other than that, another approach would be to actually reach out to the third-party app developer for assistance on how to proceed with those errors. |
| Symptom Severity | New: Severity 3 - Minor [ 15832 ] | |
| Affects Version/s | New: 3.0.0 [ 54800 ] | |
| Affects Version/s | New: 4.0.0 [ 81612 ] | |
| Affects Version/s | New: 5.0.0 [ 99898 ] | |
| Affects Version/s | New: 5.17.2 [ 108793 ] | |
| Workflow | Original: JAC Suggestion Workflow 3 [ 4477247 ] | New: JAC Bug Workflow v3 [ 4481345 ] |
| Issue Type | Original: Suggestion [ 10000 ] | New: Bug [ 1 ] |
| Priority | New: Low [ 4 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Needs Triage [ 10030 ] |
| Description |
Original:
h3. Problem
Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types. h3. Suggested Solution _When removing a custom field that is not in use anymore, any reference to it should also be removed from the database_ h3. Why This Is Important _Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:_ {code}2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request] Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support' com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'{code} h3. Workaround * A possible workaround is to manually delete the records from the "AO_54307E_VIEWPORTFIELD" table. However, please be careful when doing so, as that table holds data related to all custom fields in use by any Request Type. * Other than that, another approach would be to actually reach out to the third-party app developer for assistance on how to proceed with those errors._ |
New:
h3. Problem
Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types. h3. Suggested Solution _When removing a custom field that is not in use anymore, any reference to it should also be removed from the database_ h3. Why This Is Important _Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:_ {code}2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request] Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support' com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'{code} h3. Workaround * A possible workaround is to manually delete the records from the "AO_54307E_VIEWPORTFIELD" table. However, please be careful when doing so, as that table holds data related to all custom fields in use by any Request Type. * Other than that, another approach would be to actually reach out to the third-party app developer for assistance on how to proceed with those errors. |
Jira should remove all references to a custom field when deleting custom fields from the Jira UI. Jira Admins should not have to take Jira down and manually remove this information from the Jira database.