Question
Hello! My team has been experiencing an issue where, when Issues are deleted in Jira, they remain in DevLake frozen in whatever their most recent status pre-deletion was, disappearing from all post-deletion results in the Raw layer but staying present in the Tool and Domain layers. Is the only way to have these issues that no longer exist in Jira be removed from DevLake to do a periodic full-refresh? Or, is there a Scope || Advanced Blueprint configuration || customize plugin method to configure DevLake to do cleanup for only these issues autonomously.
Question
Hello! My team has been experiencing an issue where, when Issues are deleted in Jira, they remain in DevLake frozen in whatever their most recent status pre-deletion was, disappearing from all post-deletion results in the Raw layer but staying present in the Tool and Domain layers. Is the only way to have these issues that no longer exist in Jira be removed from DevLake to do a periodic full-refresh? Or, is there a Scope || Advanced Blueprint configuration ||
customizeplugin method to configure DevLake to do cleanup for only these issues autonomously.