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

Community

Connector Improvement: Jira Sprints completed date inconsistent

Answered
Kelvin Touchette User

The completed date for a sprint isn't always marked and was told by support that this is an issue that needs to be registered as a feature improvement. This look like a failure to update a sprint unless an issue related to the sprint has been updated after the sprint since sprints are not directly queried for changes.

"Unfortunately Jira does not provide endpoint to know which sprints were changed.

There are two ways to keep sprints updated:

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Anna User

    Hi Kelvin, thanks for your request. We may be able to add sprint updates to our webhooks– can you tell me more about your use case? How often are sprints being updated without any issues in the sprint changing?

  • Kelvin Touchette User

    We've only noticed this once in the past month, but we only recently rolled out the report to end users. Typically the Sprint is marked as completed though and unless issues weren't completed and are moved to a future sprint, there wouldn't be updates to the issues.

  • Anna User

    Thanks Kelvin. I'll add this to our backlog and continue to monitor this ticket for upvotes, which help us prioritize requests.

  • Kelvin Touchette User

    Just a follow up that this was noticed with 2 more sprints this month, where the completed date remained empty despite the sprint being closed. This issue does remain a problem. Being able to do a historic sync of just the sprint table would make it easier to clean this up, if that would be an easier possibility. The full historic sync takes several days and isn't something we'd want to do regularly.

  • Ken Hurst-Brodie User

    Hi, @.... I ran into this issue as well. Sprints are particularly impacted by this, as sprints with all issues resolved before the close of the sprint won't trigger the sprint to get updated by Fivetran. So, if a team is working perfectly, the sprint data will necessarily be out-of-date.

    Perhaps you could consider updating the Connector page to note this behavior?:
    https://fivetran.com/docs/applications/jira

    For data consumers, having unreliable data is often worse than not having the data at all, so it's especially important to note when there is a strong possibility of a data inconsistency.