Iteration ids are incorrect via API
Hi,
Iteration ids gave by API are incorrect, they are equals of the iteration number (not their real id)
Please, can you fix that?
Thanks for this great product!
Thibaud
Iteration ids gave by API are incorrect, they are equals of the iteration number (not their real id)
Please, can you fix that?
Thanks for this great product!
Thibaud
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
-
Inappropriate?Iterations are dynamically calculated and do not have a real "id" that doesn't change. We only added the "id" element equivalent to the iteration number so that ActiveResource will work at all. API users can retrieve all or a subset of iterations via the "group, limit and offset" parameters (see examples below).
You can find more information in the iterations section of the API help page http://www.pivotaltracker.com/help/ap....
#ActiveResource Examples
require 'rubygems'
require 'activeresource'
class Iteration < ActiveResource::Base
self.site = "http://www.pivotaltracker.com/services/v2/projects/:project_id"
headers['X-TrackerToken'] = 'TOKEN'
end
# retrieving all iterations
Iteration.find(:all, :params => {:project_id => PROJECT_ID})
#retrieving a subset of iterations via the limit and offset parameters"
Iteration.find(:all, :params => {:project_id => PROJECT_ID, :offset => 3, :limit => 2})
#retrieving a subset of the 'backlog' via the group limit and offset parameters"
Iteration.find(:all, :params => {:project_id => PROJECT_ID, :group => 'backlog', :offset => 1, :limit => 2})
1 person says
this solves the problem
-
Inappropriate?Ok, thank you Mark!
Loading Profile...


