sayeedhussain opened a new issue, #7006:
URL: https://github.com/apache/incubator-devlake/issues/7006

   <!--
   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
   I am importing incidents into devlake using webhooks as my incident 
management tool (ServiceNow) is not supported by Devlake yet. 
   
   When I import, the issue is getting created in the `issues` table in mysql 
correctly. However, there is no way to map that issue to a deployment for the 
`Change Failure Rate` metric whose sql query seem to be querying 
project_issue_metrics table to perform a join to tie an issue to a deployment. 
Refer https://devlake.apache.org/docs/Metrics/CFR/#how-is-it-calculated.
   
   In my case, the project_issue_metrics table is empty and logically so 
because the webhook is only populating issues table.
   
   How to solve this?
   
   thanks in advance.
   
   ## Screenshots
   If applicable, add screenshots to help explain.
   
   ## Additional context
   Add any other context here.
   


-- 
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]

Reply via email to