dosubot[bot] commented on issue #8150:
URL: 
https://github.com/apache/incubator-devlake/issues/8150#issuecomment-2426322486

   <!-- Greeting -->
   Hey @Adibov! I'm here to help you with any bugs, questions, or contributions 
you have. Let's work together to solve this issue.
   
   <!-- Answer -->
   I found a similar closed issue that might be relevant to your concern: 
[Feature][DORA] Update the logic for metric `lead time for 
changes`](https://github.com/apache/incubator-devlake/issues/3516). This issue 
was closed by a pull request that updated the logic for change lead time 
<sup>[[1]](https://github.com/apache/incubator-devlake/issues/3516)</sup>.
   
   Regarding your specific issue, the current logic in the DORA plugin for 
matching incidents with deployments is based on timestamps. Incidents are 
related to the last deployment on the project with a timestamp that is before 
the incident's timestamp. This logic does not currently consider the time 
length between deployments and incidents 
<sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v1.0/Plugins/webhook.md)</sup>.
   
   There is no existing configuration option in the DORA plugin for setting 
time constraints between deployments and incidents 
<sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v1.0/Plugins/webhook.md)</sup>.
 However, you mentioned that you are willing to submit a PR, which could be a 
great opportunity to introduce such a feature. You might consider adding a 
configurable time constraint to the `ConnectIncidentToDeployment` function in 
`incident_deploy_connector.go`, which is responsible for connecting incidents 
to deployments 
<sup>[[3]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/dora/tasks/incident_deploy_connector.go)</sup>.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
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: dev-unsubscr...@devlake.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to