Support for Atlassian Server Products (and apps like BigPicture) has ended in February 2024.
Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email support@appfire.com
Jira Corrupted Index
In general, if you see any symptoms that your Jira index is corrupted (for example, your JQL queries will return wrong data), disable BigPicture, perform Jira reindex, and enable BigPicture back.
Work breakdown structure data is stored in the BigPicture table called:
T_DEP_STATE_VERSION
T_DEP_TREE_EVENT
T_DEP_LINK_EVENT
T_DEP_NODE_SIBLINGIf you have a backup that contains such a table, your WBS can be restored.
Maintaining a Jira index is critical - when the index is corrupted, synchronizing tasks can result in data loss (existing task hierarchy is changed). When the index is corrupted, JQL does not work, and the plugins treat all the issues as new during the synchronization; this means that the task structure based on artificial tasks is changed during a sync. The old structure is lost.
More about Jira index corruption can be found in Atlassian documentation:
Impact on synchronization
Full synchronization is not run when BigPicture gets information about the corrupted index from the Jira API. A user can perform a Jira reindex; this should solve the corrupted index problem. Users can also continue without reindexing, which can cause irreversible and unintended changes in Box scope.