Pickler can't seem to pull epics

[dougalcorn]

To be honest, I'm not sure the best workflow here. I have not used pickler regularly for a single project yet. There's some disconnect between a "feature" as a larger set of functionality and a "story" as a discrete, verifiable unit of work. I'm trying out using the epic as the larger feature made up of many stories. What doesn't work as well is having pickler pull all the individual stories and creating .feature files. I think I'd rather have one feature file for the epic.

My understanding is that is may be hard to link scenarios in a feature file to individual pivotal stories. I'm not asking for that. I'd like to be able to pull epics by their id and just manually note that some of the scenarios belong to some pivotal story. But the overal Gherkin for the feature would live in the description of the epic.

Right now we try to pickler pull <epic id> and get:

Resource not found

[tpope]

Using epics as the base for synchronization is an interesting idea that wasn't really a possibility when I first created Pickler. Can you figure out a high level game plan for what changes would be needed to make this possible?

[dougalcorn]

I've talked about this with @mguterl and @cdmwebs. Unfortunately, it seems the epics aren't yet exposed via API:

http://community.pivotaltracker.com/pivotal/topics/will_epics_ever_be_included_in_your_api_or_import_export_feature http://community.pivotaltracker.com/pivotal/topics/can_you_create_modify_epics_through_the_api

Doug Alcorn (513) 295-2844

[cantonic]

it seems like it is possible now with the REST API v5: https://www.pivotaltracker.com/help/api/rest/v5#Epics