Currently, the JIRA REST API returns both JSON and string representations of a sprint when requested.
We're planning to deprecate the string representation of a sprint, however the JSON representation lacks some data that the string provides.
As now changes have been rolled out when you plan to switch the default representation of Sprint field (if you still have such plan)?
@blewandowski while implementing the JSON representation of Sprint field a question arose - in Sprint REST API endpoint (https://docs.atlassian.com/jira-software/REST/2017-09-19T00:01:13Z/#agile/1.0/sprint-getSprint) board ID is returned in field 'originBoardId'. In issue Sprint JSON representation the field is called 'boardId'. What's reason for the difference?
created by different teams at different moments. We are aware of this inconsistency, but it isn't a major issue so are not planning to fix this in the near future.
Will this be fixed for only cloud version of Jira?
Or will there be any Jira Server version for which this will be fixed?
This ACJIRA project is for tracking bugs and improvement requests specifically for Atlassian Connect in Jira Cloud. At this moment there is no dedicated project for collecting Jira Server Ecosystem issues here in ecosystem.atlassian.net and the best I could advise you is to contact Atlassian Support who could help you with answering your questions.