We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      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

      1. Add a component to an issue
      2. Archive the component
      3. 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

      1. 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);
      2. Reindex Jira

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                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

                1. Add a component to an issue
                2. Archive the component
                3. 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

                1. 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);
                2. Reindex Jira

                        Unassigned Unassigned
                        malmeida Marcus Silveira
                        Votes:
                        21 Vote for this issue
                        Watchers:
                        28 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            malmeida Marcus Silveira
                            Affected customers:
                            21 This affects my team
                            Watchers:
                            28 Start watching this issue

                              Created:
                              Updated: