You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we fetch all projects, issues, etc for the specified group when tap-gitlab runs.
With the introduction of Epics, there is a possibility that some issues in an epic reside in a project outside of the group extracted.
An example can be seen by one of the epics in the Meltano Group.
The project some of the issues reside was moved out of the Meltano Group resulting in those issues being referenced by the Epic, but not fetched by tap-gitlab as they are not part of the Group fetched.
We should recursively identify such issues and fetch them and their relevant entities when Epics are extracted.
The text was updated successfully, but these errors were encountered:
changed title from {-Also expor-}t issues and associated entities for entities outside of the fetched group that belong to an Epic to {+Extrac+}t issues and associated entities for entities outside of the fetched group that belong to an Epic
In GitLab by @iroussos on Jun 14, 2019, 07:21
Currently, we fetch all projects, issues, etc for the specified group when
tap-gitlab
runs.With the introduction of Epics, there is a possibility that some issues in an epic reside in a project outside of the group extracted.
An example can be seen by one of the epics in the Meltano Group.
The project some of the issues reside was moved out of the Meltano Group resulting in those issues being referenced by the Epic, but not fetched by
tap-gitlab
as they are not part of the Group fetched.We should recursively identify such issues and fetch them and their relevant entities when Epics are extracted.
The text was updated successfully, but these errors were encountered: