Move to agile API broke search and potentially other interfaces

[softprops]

It seems this change #20 changed the base url for all endpoints. Some interfaces like search are not supported by the agile API. Let's find a way to accommodate both

[r-darwish]

I'm using a JIRA instance which doesn't have the agile API, so I have to patch Goji locally in order to be able to even work with my company's JIRA.

We can have an enum to control whether Goji should use agile or api, but if we don't implement any agile specific features, then shouldn't Goji just use api everywhere, and only use agile in the future, when Agile specific features are implemented?

[softprops]

I think where youre going with this. If you have some ideas I'd be up for pull requests I myself only use the default API endpoints so I have less visibility into other jira installations. I'm wondering if it makes sense to export separate interfaces for both. Besides the path do parameters and response structures differ between the two?

[r-darwish]

Sorry for taking long to respond. I am not the maintainer of JIRA where I work, but I think we also use the default API, we just don't seem to have the agile API ready.

It probably makes sense ti export seperate interfaces for both of them. I just don't know what are the unique methods of the Agile API.