Connector Improvement: Support Epic Label Mapping with Shortcut Connector
CompletedI just discovered another small gap in the shortcut connector that I'm hoping you can help me solve. Given how quickly your team solved a similar issue, I'm hoping you might be able to quickly solve this problem as well.
Another crucial data point for us are epic labels (see api docs for top level json key "labels" here.
In shortcut, epics have labels. The shortcut connector supports epic and label datasets but doesn't provide a way to link the two.
In the shortcut api, this datapoint, similar to the story owner response attribute for GET story, is a simple array of label metadata for the GET epic endpoint. Each item in this array contains a label id which would allow us to link to the labels datatset provided by the connector were this field ingested.
An analogous data structure would be the story_label table created by the connector which supports a similar mapping, but for stories.
An analogous data structure would be the story_label table created by the connector which supports a similar mapping, but for stories.
It seems obvious this data should be ingested into a new epic_label table via the shortcut connector
Is this something fivetran could help us with?
Is this something fivetran could help us with?
-
Official comment
Hi Gilbert,
Thank you for pointing this out. We have now added the necessary functionality to support this request. Please feel free to let us know if you have any questions/concerns.
Thank you,
Please sign in to leave a comment.
Comments
1 comment