## Current situation: 1. the Jira API endpoints have a vast set of supported parameters (for POST requests there is a possibility to specify also GET parameters) 2. the `Api` class methods that perform GET Jira API calls provide limited configurability, e.g. * only several common parameters can be specified * sometimes there is `$params` parameter for specifying additional query params 3. the `Api` class methods that perform POST Jira API calls provide limited configurability, e.g. * only several common parameters can be specified * sometimes there is `$params` parameter for specifying additional POST data * no way to specify query parameters This has resulted in some issues: * #154 * #153 * #191 ## Solution 1. #220 2. #223
Current situation:
Apiclass methods that perform GET Jira API calls provide limited configurability, e.g.$paramsparameter for specifying additional query paramsApiclass methods that perform POST Jira API calls provide limited configurability, e.g.$paramsparameter for specifying additional POST dataThis has resulted in some issues:
Solution