Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Jira Connector: Agile Metrics need more tables and dimensions imported

Not planned
Robert Gosselin User

Hi,

As part of producing Agile metrics for our teams using the Jira Connector, we need more than what's provided in the current ERD for the Jira Connector.

In particular, a Scrum board will have multiple sprints and the current ERD does not bring the relationship between issues being in multiple sprints. It would be great to have another dimension(s) for each issues that list the sprints they were part of. In fact, it would be more useful to have a sprint table that lists all issues per sprints with their start, end date of being in the sprint, when they were completed during the sprint...

The way the data works is this way:

There are multiple ways to get what Atlassian calls the Agile information into the ingestion of data, but w/o that information, it will be impossible to product agile reports like velocity, completion rate, what epics teams are working on during certain sprints, how spread or how focused they are in their work, or try to predict delivery date based on those information and more.

If you technical team wants to discuss further, I’m more than happy to get on a video chat and discuss the needs and other issues I’ve found.

Thanks

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Frank Fivetranner
    • Edited

    Hi Robert,

    Currently our connector already supports the mapping of issues to sprints. Here's a query that hopefully will help

    WITH sprint_field AS ( SELECT id as fieldId FROM digital-arbor-400.jira.field WHERE name = "Sprint" )

    SELECT imh.issue_id, s.* FROM digital-arbor-400.jira.issue_multiselect_history AS imh JOIN sprint_field AS sf ON imh.field_id = sf.fieldId JOIN digital-arbor-400.jira.sprint AS s ON CAST(imh.value AS STRING) = CAST(s.id AS STRING) WHERE imh.value IS NOT NULL;

    Let me know if further clarification would help.

    Thanks,
    Frank

  • Erin Fivetranner

    Hi Robert - 

    My name's Erin and I'm the Product Manager for Engineering Connectors. This is an interesting feature request and we've seen a few other requests for this in the past. I'll add this to our backlog to research more into the technical feasibility. 

    Thanks so much,

    Erin  

  • Robert Gosselin User
    • Edited

    Thanks Erin!

    Whenever you need, I'd love to beta test any improvments you can make.

    The other place to look for inspiration might be this DBT: 
    https://hub.getdbt.com/fivetran/jira/latest/

    I'm not familiar with dbt so not sure how to use that, but it seems to do part of the job.

    The other part that's definitely needed would be to add the ability to ingest custom fields. Almost every jira instance is customized with custom fields to help with particular of the business and those are very important to dashboards and reports (aka, if you have Themes or Customer Segments you want to organize your work against).

    Robert

    PS: I've also noticed that the Projects Table link you have in the Jira ERD points to deprecated Atlassian APIs; hopefully, your team is working on updating to the new API.