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.