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

Community

Connector Improvement: Jira connector, add column ACTIVATED_DATE

Completed
Robert Haycock User

For the Jira connector, under the Sprint table, we are seeing a start_date (which is the date that a sprint is intended to start), an end_date (the date the sprint is intended to end), and a completed_date (the date that a sprint actually ends). But we are not seeing the activated_date (the date a sprint actually starts, which may be different than the intended start date). This is not a custom field, but rather, a data point associated with the status of an object in Jira (in this case, the object is a sprint). This column is available and visible in the actual Jira production database.

I am not seeing this column on the ER diagram on Fivetran's documentation, and I see no option to import it in the Fivetran UI for connectors. Please add this column as it makes no sense to have the completed_date but not the activated_date.

Please sign in to leave a comment.

Comments

6 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hey Robert - Thanks for submitting this feature request. 

    At this time Atlassian doesn't support the `activated_date` in their REST API (See Docs). However the `start_date` field gets overwritten with the actual sprint start date when a user clicks the start sprint button in the Jira UI. 

    We also have recently updated our logic for capturing changes to the sprint endpoint using webhooks, so this field should be accurately updated when a sprint actually begins. 

    Best, 
    Erin

  • Robert Haycock User

    Erin thanks for the response. We have noticed that our start date is not updating as you mentioned.

    In our destination database, one of our sprints shows as started on 10 MAY 2022 at 22:13:00 UTC. But when we log into Jira, the UI tells us a planned start date of 10 MAY 2022 at 22:13 UTC (which makes sense), with an actual start date as 10 MAY 2022 at 16:29 UTC.

    In our destination database, the column `_fivetran_synced` shows 27 JUNE 2022, so there has been plenty of time to update. It seems the `start_date` column was not updated. Why would this be?

  • Erin Fivetranner

    Hi Robert -

    I misspoke earlier. The `activated_date` is a valid field for Jira on-premise editions. For consistency across both the on-premise and cloud editions, we will use the `activated_date` field and over-ride the `start_date` when the `activated_date` is finally set. 

    We will be taking this task up in an upcoming sprint. 

    Best,
    Erin

  • Erin Fivetranner

    Hi all - This has been implemented. 

    You can review the release notes for this in our change log. 

    Best,

    Erin

  • Robert Haycock User
    • Edited

    Erin can this be run on Jira Data Center? I know there are differences between Data Center and Server, but both are on prem I believe. Moreover, how do we enable this column in the Fivetran UI? Is it as simple as navigating to the connector and selecting the checkbox for the activated date column?

  • Charlie Cao User

    Hi Erin,

    Can we re-open the discussion for this feature? It doesn't make sense to me that we are deleting data (overwriting `start_date` with `activated_date`) from the Jira on-premise edition just to stay "consistent" with the lack of such data on the Jira cloud edition. Could you separate these two fields for both editions and just leave `activated_date` NULL if there's no data?

    I made a Feature Request here: 
    https://support.fivetran.com/hc/en-us/community/posts/16288956283671-Connector-Improvement-Separate-start-date-and-activated-date-in-sprint-table-for-Jira-Data-Center-On-Premise

    Charlie