-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: REST API
-
None
-
1
As a typical developer, scripter, or user of ETL (extract, transform, load) tools, I need to ability to include parameters specific to Changelog History data in the REST API call so that I can limit the volume of JSON data returned.
We are a large enterprise using the REST API to pull Jira data into Alteryx to perform ETL functions in preparation for loading the transformed data into Tableau for reporting. Currently there is a large volume of Changelog History data returned when using "...?expand=changelog". Quite often the vast majority of changelog data is not needed or wanted, so we need the ability to limit what changelog data is returned in the following ways:
- Changes to a specific field or list of fields (both system and custom fields; could be a single field or a comma-separated list of fields)
- Changes made to a specific field match or are similar to <text>, e.g. ~"<text>"
- Changes made to a specific field equal an option or comma-separated list of options for that field
- Changes made to a specific field from one option to another option, e.g. from <option A> to <option B>
- Changes made within certain time frames, e.g.: -1w, EndOfMonth(), before or after <date>, between date range, etc.