Connector Improvement: Request Issue-Sprint Mapping for JIRA Connector
Not plannedThe current structure does not support direct mapping between the ISSUE and SPRINT tables.
While an indirect mapping via PROJECT_BOARD is possible, it leads to incorrect associations. Each issue appears linked to all sprints rather than its actual sprint.
We need the issue table updated to include accurate sprint details for each issue to support reliable sprint-level reporting.
-
Official comment
Hi Wai,
While this specific enhancement isn’t currently available in the JIRA connector, you can achieve similar results using existing tables and a transformation step.
Here's an example query to achieve this mapping:
WITH sprint_field AS ( SELECT id as fieldId FROM
digital-arbor-400.jira.fieldWHERE name = "Sprint" )SELECT imh.issue_id, s.* FROM
digital-arbor-400.jira.issue_multiselect_historyAS imh JOIN sprint_field AS sf ON imh.field_id = sf.fieldId JOINdigital-arbor-400.jira.sprintAS s ON CAST(imh.value AS STRING) = CAST(s.id AS STRING)With this provided transformation, I'm closing this request for now. Please let me know in this thread if there are further questions.
Thanks,
Frank -
Hi Wai Chin,
Thank you for submitting this feature request and sharing your idea to improve the JIRA connector with issue-sprint mapping and we will assess the feasibility this request. As a short term workaround do you know if its possible to have the sprint exposed as a custom field on the issue itself for your organization?
I’m also curious to learn more about your use case. Could you share a bit more about what problem you are trying to solve or how improved issue-sprint mapping would benefit your workflows? Any additional details on your requirements or an example of the reporting or analytics you’d like to achieve would be very helpful.
We appreciate your input and will keep this thread updated with any progress or news regarding this request. Thank you again for helping us make Fivetran better!
Best regards,
Frank Zhu
Please sign in to leave a comment.
Comments
2 comments