Community

Connector Improvement: Jira Issue story points

Answered

Jameel Al-Aziz User

December 08, 2022 05:23

Related to https://support.fivetran.com/hc/en-us/community/posts/5255905367319-Connector-Improvement-Adding-Custom-Fields-to-Jira-Issue-?input_string=Jira%20Issue%20story%20points. It would be great if story points were synced on the issue directly.

Please sign in to leave a comment.

Comments

2 comments

Official comment

Erin Fivetranner
- December 29, 2022 19:12
Hi Jameel -

Thanks for submitting this feature request! How / if we can sync story points depends on how the Story Points are represented in your system. We can support Story Points in Jira if they are represented by float values. Are you representing them differently in your Jira instance? I would be curious to understand this so we can identify if there is another solution.

Best,

Erin

Jameel Al-Aziz User

December 29, 2022 22:16

We use the Jira Agile Story Points field. Currently, I can "join" story points to the issue using the follow SQL query in Snowflake:

SELECT *
FROM "FIVETRAN"."JIRA"."ISSUE" i
LEFT JOIN (
    SELECT DISTINCT ISSUE_ID, FIRST_VALUE(VALUE) OVER(PARTITION BY ISSUE_ID ORDER BY TIME DESC) as STORY_POINTS
    FROM "FIVETRAN"."JIRA"."ISSUE_FIELD_HISTORY" fh
    LEFT JOIN "FIVETRAN"."JIRA"."FIELD" f on f.ID = fh.FIELD_ID
    WHERE f.NAME = 'Story Points'
) sp on sp.ISSUE_ID = i.ID

However, that's not very "friendly" for most passive queriers, so were hoping the field could be elevated directly onto the issue as some other fields are.