hezyin commented on issue #1681:
URL:
https://github.com/apache/incubator-devlake/issues/1681#issuecomment-1178336607
@keon94 Hi Keon, thanks for putting together this proposal. I'll summarize
my understanding and questions below.
1. Right now we collect regular Jira issues by board. A regular Jira issue
that belongs to an epic issue will have a non-empty`epic_key` field.
2. Your plan first collects regular Jira issues as before. Then a new
collector gathers all non-empty `epic_key`s from _tool_jira_issues table, and
call `agile/1.0/epic` with those epic keys.
3. Then a new extractor transforms raw epics to _tool_jira_issues,
_tool_jira_board_issues, and etc.
4. The same old converter transforms tool layer tables to domain layer tables
Questions:
1. Can you elaborate a bit more on the optimization you mentioned in your
point 1? Having trouble understanding that part.
2. How do we figure out which board an epic belongs to and create entries in
_tool_jira_board_issues accordingly? Does `agile/1.0/epic` give out this info?
3. Where are the dupes that need to be dealt with in the new extractor
coming from?
--
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]
