How to map sprints to boards

We are building out our analytics repository with Jira data. One of the things I can’t seem to figure out how to do with the current connector is map between sprints and boards. All sprints can be part of one or more boards. However, there doesn’t seem to be any way in the current data to determine this. The sprint metadata includes ‘originboardid’, but that is (from what I can tell) the original board it was part of and not the current board. We have many sprints that are not part of the originboardId.

The Jira API always has sprints beneath a board, and the connector code does query for sprints beneath the board endpoint:

    def path(self, stream_slice: Mapping[str, Any], **kwargs) -> str:
        return f"board/{stream_slice['board_id']}/sprint"

However, this board_id never propagated into the sprint metadata. With BoardIssues, this is done explicitly:

    def transform(self, record: MutableMapping[str, Any], stream_slice: Mapping[str, Any], **kwargs) -> MutableMapping[str, Any]:
        record["boardId"] = stream_slice["board_id"]
        record["created"] = record["fields"]["created"]
        record["updated"] = record["fields"]["updated"]
        return record

Is there any way to determine the board ↔ sprint mappings from the data current available to the connector? If not, is any reason why boardid couldn’t be added to sprints as well, similar to what’s been done for board issues?

Note that as a workaround, I can join board_issues with sprint_issues and select distinct (board, sprint) tuples, but this assumes that there is always at least one issue assigned. It would much cleaner if we could just look at the natural hierarchy exposed by the Jira API.

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team