hezyin commented on issue #1681: URL: https://github.com/apache/incubator-devlake/issues/1681#issuecomment-1179489812
@keon94 Did you mean _tool_jira_board_issues by _tool_jira_board in the following sentence? > @hezyin You understood correctly, but for (3), we shouldn't need to extract the raw epics into _tool_jira_board (as mentioned by @mindlesscloud as well), because the regular issues extractor will already have extracted all the board-relevant epics to that table. Thanks for the clarification. Let me summarize my latest understanding to make sure everyone involved in the thread is on the same page. 1. If an epic issue belongs to the Jira board that we collect regular issues from, then they're already collected by the current implementation. This issue (#1681) is really about collecting (foreign) epic issues that don't belong to the Jira board themselves but are linked to regular issues from that Jira board. 2. When we collect the epic issues by going through the epic_key field in _tool_jira_issues, we can skip the ones that actually belong to the Jira board we collected. This can be checked by querying _tool_jira_board_issues. 3. The dedupe step can be done at the collector stage (when going through the epic_key field) instead of the extractor stage. 4. If foreign epic issues don't have corresponding entries in _tool_jira_board_issues, then we need to be careful when writing SQL queries for dashboards since right now many SQL queries use a board as a filter. @Startrekzky Please advise if there's any misunderstanding in the summary above. @klesh @Startrekzky @terrymanu @keon94 -- 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]
