-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
8.1.0, 8.5.0, 8.5.3
-
8.01
-
24
-
Severity 2 - Major
-
24
-
Issue Summary
Deleting components that have been archived does not remove the Issue association from the nodeassociation table.
This can lead to gadgets showing a different number of issues without components than what's seen in the Issue navigator.
Steps to Reproduce
- Add a component to an issue
- Archive the component
- Delete the component
Expected Results
Component is deleted and any association to it is removed
Actual Results
Component is deleted but nodeassociation table still has the link between the issues and component.
Workaround
- Delete the orphaned rows manually with the SQL query below
delete from nodeassociation where source_node_entity = 'Issue' and sink_node_entity = 'Component' and sink_node_id not in (select id from component);
- Reindex Jira
- is caused by
-
JRASERVER-10507 Archive project components
- Closed
- relates to
-
JRASERVER-15750 Component delete operation leaves orphaned records in nodeassociation table due to non-atomic writes
- Closed
-
SONIC-139 Loading...
- is cloned by
-
FLASH-2605 Loading...