keon94 commented on issue #1681: URL: https://github.com/apache/incubator-devlake/issues/1681#issuecomment-1177097071
Going off of the Jira [API docs](https://docs.atlassian.com/jira-software/REST/7.0.4/#agile/1.0/issue-getIssue), here's what I think: 1. We need a new Collector for epics. This collector will need to references the issues tools table to determine which epic IDs it needs to query (by calling agile/1.0/epic) - we can't rely on the board ID to fetch the epics which is the whole point of this feature. (*) We may be able to further optimize this by also outer-joining the results on the issue_id field of _tool_board_issues to exclude any epic we've already taken care of through the Issues collector/extractor. 2. We'll use a new Extractor for epics. This will convert the raw epics into issues and store them in the _tool_jira_issues table as normal. These raw epics may contain duplicates so we will dedupe them here. If we follow (*) there won't be any DB rewrites either. I think that should be sufficient as far as our goal of getting these "foreign-board" epics included. The existing Issue converter will continue as normal and treat these epics like the other issues, so no changes needed there. @Startrekzky @mindlesscloud do you guys agree? -- 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]
