nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Getting Sprint's start date and end date programatically

unknown

Hello my friends,

We are using the Jira REST API to get information about our Sprints into another tool. We know that the Sprint's start date and end date is information stored in GreenHopper, so we understand why they are not part of the response to the GET version request. Is there any other way of getting that information through any other interface?

Cheers,

Diego Alonso

Accepted answers

Wojciech Seliga

Hi,

You can retrieve GH Sprint's start date and end date from com.pyxis.greenhopper.jira.configurations.ProjectConfiguration#getVersionStartDate and getVersionEndDate - but that requires writing a plugin on the server side or extending GH directly (and building it from the source code). You can retrieve ProjectConfiguration using com.atlassian.greenhopper.service.configuration.ConfigurationService which could be autowired to your own class if you import it in your atlassian-plugin.xml.

From this step exposing start date and end date via your own REST module looks like a piece of cake

All comments

Jeremy Largman

Hi Diego,

The closest I can come up with is getting the RemoteVersion through JIRA's API:

http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/index.html?com/atlassian/jira/rpc/soap/JiraSoapService.html

It's got getReleaseDate(), but I realize that's not quite what you're after. I'm leaving this as a comment so the question stays unanswered. Nice to hear from you!