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

[GitHub] [incubator-devlake] Startrekzky opened a new issue, #4769: [Feature][Schema] Add a table for incidents

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

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Use case
   
   As an engineer, I want to query incident metrics from DevLake faster.
   
   ### Description
   
   Currently, incidents are stored in table.issues with type = "INCIDENT", which is not that intuitive.
   
   This proposal is to store Jira/GitLab/GitHub/PagerDuty/ServiceNow incidents in a new table called "incidents" or "ims_incidents" (ims stands for incident management system). If you’re using other tools like Jira/GitLab/GitHub to manage incidents, please also store a copy of incidents in table issues with type = "INCIDENT", since they're also Jira/GitLab/GitHub issues.
   
   This means that 
   - [ ] design a domain layer table "incidents" or "ims_incidents" based on [PaterDuty](https://github.com/apache/incubator-devlake/issues/3498) and [ServiceNow](https://github.com/apache/incubator-devlake/issues/4234) incidents' attributes
   - [ ] implement plugins' transforming logic: any operations to incidents will directly touch table.ims_incidents
   - [ ] update the queries to get incidents in the DORA dashboard
   - [ ] update the "refdiff" plugin about incident-deployment mapping logic
   - [ ] deal with historical "incidents" from v0.17 or prior versions 
       - [ ] historical incidents from PagerDuty should be MOVED from "issues" to "ims_incidents"
       - [ ] historical incidents from Jira/GitLab/GitHub should be COPIED from "issues" to "ims_incidents"
   - [ ] update related docs
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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.apache.org

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


[GitHub] [incubator-devlake] github-actions[bot] commented on issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4769:
URL: https://github.com/apache/incubator-devlake/issues/4769#issuecomment-1616216255

   This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.


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


[GitHub] [incubator-devlake] github-actions[bot] commented on issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4769:
URL: https://github.com/apache/incubator-devlake/issues/4769#issuecomment-1536930025

   This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.


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


[GitHub] [incubator-devlake] github-actions[bot] closed issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4769: [Feature][Schema] Add a table for incidents
URL: https://github.com/apache/incubator-devlake/issues/4769


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


[GitHub] [incubator-devlake] Startrekzky commented on issue #4769: [Feature][Schema] Add a table for incidents

Posted by "Startrekzky (via GitHub)" <gi...@apache.org>.
Startrekzky commented on issue #4769:
URL: https://github.com/apache/incubator-devlake/issues/4769#issuecomment-1570239182

   Although we all agree that we should add a table called `incidents`, @klesh seems to prefer keeping this table in the `issue tracking domain` rather than creating a new `incident management domain` for the sake of the simplicity of the data schema for now, until there're strong use cases for an individual domain.
   
   What are your thoughts?  @keon94 @hezyin 


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


[GitHub] [incubator-devlake] github-actions[bot] closed issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4769: [Feature][Schema] Add a table for incidents
URL: https://github.com/apache/incubator-devlake/issues/4769


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


[GitHub] [incubator-devlake] github-actions[bot] commented on issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4769:
URL: https://github.com/apache/incubator-devlake/issues/4769#issuecomment-1526803894

   This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.


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


[GitHub] [incubator-devlake] github-actions[bot] commented on issue #4769: [Feature][Schema] Add a table for incidents

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4769:
URL: https://github.com/apache/incubator-devlake/issues/4769#issuecomment-1627553570

   This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.


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