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

Community

Connector Improvement: Jira History

Planned
Kelvin Touchette User

With the JIRA connector, in the tables ISSUE_FIELD_HISTORY and ISSUE_MULTISELECT_HISTORY, please include the old value / new value fields instead of just a single value field in the data retrieved from the API. Both of these are available in the API and are particularly helpful in the case that we have more than one history record at the same time/field, to determine which record is the last one active for that time.

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Drew Fivetranner

    Kelvin Touchette The most recent version should be marked with the most recent `updated_at` timestamp.

    Is the challenge that you are unable to easily identify which record is `Active`? Would providing that field be useful?

  • Kelvin Touchette User

    The problem is that you'll have some records that have the same "created" timestamp since the times are only tracked to the second and not millisecond. If I have a from/to value, I can try to put the values together to determine the sequence that events occurred, otherwise it's uncertain. For some context, we're trying to report on things like if a Jira issue is in a certain state, are people adding comments regularly. So we need to be able to see a full history of the issues along with several custom fields and not just be certain of the latest version.

    We're able to get the max value of the "created" timestamp per issue/field, but having an active flag would be useful to not have to do this calculation afterwards and in cases like I mentioned where a field may have been changed more than once within the same time.

    I believe the rapid field changes are related to automations rather than an actual user changing the data so quickly.

  • Jacob Adler User

    Tim from Fivetran Support routed me here as we have been reporting this exact problem.

    In our use case, where more than one component can apply at one time, there needs to be a valid_from and valid_to combination of fields, or an array of the components at a given time as Kevin suggests.

    Currently, the way Fivetran approaches it is completely unacceptable as we are unable to report on components at all, while that is the #1 analysis request from my company's support team.

    Please consider revising the ERD to make the data usable in this way.

  • Kelvin Touchette User

    Drew are there any updates on this feature request?

  • Anna User

    Hi Kelvin Touchette, we are planning to introduce History mode for these tables this quarter, which will mark the most recently updated record as `Active`. You can read more about the feature here: https://fivetran.com/docs/getting-started/feature/history-mode.

    Thanks for your patience on this request!