Did the way the sprint_name field was handled in the API change?

Aaron Mitchell

We are using Domo to pull from the Jira API (using the custom JQL query `project = "<project name>") and visualize how many story points get completed each sprint by each developer. To do this, we used to just filter by the current sprint name, however in the last week these reports have changed to no longer display tickets that were originally added to a previous sprint and then got carried over.

In looking at the data coming back from Jira, we noticed that the carried-over tickets are now displaying the original sprint they were added to as the sprint_name, and not the most recent sprint_name. Is anyone else experiencing this?

Andy Heinzer

Hi Aaron,

If I understand the problem here, you're using another service to gather data from Jira via the API, but it seems like the name of the sprint has changed behavior here.  I am not aware of any recent changes to the way the sprints or sprint names are managed in either the JAVA API or the REST API that could possibly be in use.

Could you let me know more about which Jira API you are referring to here?  If this is the REST API, then typically we don't lookup a sprint by name, but rather by the sprintId.  Since Jira allows you to have more than one sprint with the same name, it tends to be necessary to do this so that we know we are always using a unique identifier.   For REST API, you can do this by calling the endpoint GET /rest/agile/1.0/board/{boardId}/sprint.  Granted you need to know what board that sprint exists on, and then know that boardId to make that call.  One way to do that is use the GET /rest/agile/1.0/board endpoint to find that boardId.

If this is not using the REST API, please let me know more about how API calls are being made here.  Perhaps if I can somehow reproduce the problem I can better understand what might be causing it here.

Andy