You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "Feggah (via GitHub)" <gi...@apache.org> on 2023/05/24 18:05:14 UTC

[GitHub] [incubator-devlake] Feggah commented on issue #5278: [Bug][PagerDuty] All Projects _raw_pagerduty_incidents overidden by one Project's Sync

Feggah commented on issue #5278:
URL: https://github.com/apache/incubator-devlake/issues/5278#issuecomment-1561712997

   I can also confirm that any PagerDuty Sync after the first Sync made in DevLake is not going to pull more data from PagerDuty. Instead, it will only override all `board_id` in `board_issues` to change the Service that is related to the Incident. For example:
   
   ![image](https://github.com/apache/incubator-devlake/assets/11353912/c66a9174-87ef-4c04-b07d-30332a525eb9)
   
   As you can see, the Service `PZ2SY12` is associated with all PagerDuty incidents. Then I run another Sync in another Project with another Service:
   ![image](https://github.com/apache/incubator-devlake/assets/11353912/d19e0513-8e97-4a8e-b282-45ac815573a9)
   
   And all `board_id` are overrided:
   ![image](https://github.com/apache/incubator-devlake/assets/11353912/f6148f4d-a990-49f3-81e1-63ff3738295d)
   
   Then I run another Project Sync again:
   ![image](https://github.com/apache/incubator-devlake/assets/11353912/bc0db8be-ce9a-4e76-92c2-7803a5ee3468)
   
   And all `board_id` changes:
   ![image](https://github.com/apache/incubator-devlake/assets/11353912/100320d9-7bb0-40df-baf8-081cc010a5db)
   
   I think the Projects are impacting in one another when using the PagerDuty plugin


-- 
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: commits-unsubscribe@devlake.apache.org

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