Getting Current Release / Sprint

[Colin Bowern]

What is the best way to get the current sprint from a release?  Likewise getting the current release?  I'm working on a PowerShell script for TeamCity to send a message to the REST API about a new build being created.

[Colin Bowern]

Never mind - it's a non-starter at this point because we cannot use the System account credentials to access the REST API and we are not interested in purchasing a user license just for system integration purposes.  Until the System account can be used for API access this is not relevant.

[Phillip Mullan]

This is something I've also been looking for. 

Are there REST API calls to return the Iterations or Releases that are current? (without having to compare against the start and end dates of each Release/Iteration)

Cheers

Phil Mullan

[Colin Bowern]

Good to know I'm not the only one. :)  This seems like a reasonable request to have a system account or an API key that will allow us to build integration points with the TP data set.

[Michael Dubakov]

Yes, sure.

I will check how long it may take to implement. It is definitely the reasonable request.

@mdubakov

[Alex Fomin]

Hi, 

At the moment there is now built-in check for current release/iteration in rest api. We will add a calculatable field IsCurrent to release\iteration in the nearest future as well as system user access to rest api.

Thanks,

Alex

On Wednesday, May 9, 2012 5:08:47 PM UTC+3, Colin Bowern wrote:

Good to know I'm not the only one. :)  This seems like a reasonable request to have a system account or an API key that will allow us to build integration points with the TP data set.

On Tuesday, May 8, 2012 4:46:16 PM UTC-4, Phil Mullan wrote:

This is something I've also been looking for. 

Are there REST API calls to return the Iterations or Releases that are current? (without having to compare against the start and end dates of each Release/Iteration)

Cheers

Phil Mullan

[Colin Bowern]

And this is why I'm a fan of TargetProcess... :)