-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iteration.current(@proj).stories #93
Comments
Hi Chris! Yes, this project is being maintained. |
Thanks Jason, getting the current iteration stories this way: Iteration.current(@Proj).stories where @Proj is a valid PivotalTracker::Project worked for months and now I can't gather any stories this way. I can use @Proj to find an individual story. Is there an easy way to see the URL that the gem is using to get the current stories? |
I use a proxy software like Charles (http://www.charlesproxy.com/), then force all my network connections through there. I did the following to debug:
For me, it is returning stories. Do any of the other Iteration methods work? Try |
Jason: the issue is related to the data structure returned -OR- how the response is parsed (HappyMapper or libxml). The api seems to be returning good data when trying the connection via curl. I am still tracking this down, but I will let you know what I find. Chances are, its my mistake, but I will certainly send a PR if I find otherwise. |
This returns no stories when stories exist.
Before I get into debugging the gem for this, is this gem still being maintained?
The text was updated successfully, but these errors were encountered: