gipalob opened a new issue, #9030:
URL: https://github.com/apache/devlake/issues/9030
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
