Startrekzky commented on issue #1681:
URL:
https://github.com/apache/incubator-devlake/issues/1681#issuecomment-1164403389
> @leglars No problem, since we had already collected
`jira_issues.epic_key`, what we left to do is to collect those `epic issues`
and store them into the `jira_issues` table as well, Do I understand it
correctly? @Startrekzky
Correct. I guess the flow is:
1. Collect the epic issue when a Jira issue's epic_key is not empty.
2. Store the 'epic-type' issues should be stored in tables in all 3 layers:
_raw_jira_api_issues, _tool_jira_issues, issues
a. Make sure the epic issues are de-duplicated.
b. Make sure the epic issues are enriched and converted just like other
issues.
Please let me know if the flow needs to be polished. @klesh @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]
