Connector Improvement: Jira Current Custom Field Values
Answered
It would be great if we could get a table which shows only the current Custom Field values for a given issue.
In the previous Jira connector these values were included in the `issue` table as separate fields.
Currently, we have to scan the entire `issue_field_history` or `issue_multiselect_history` tables and select the record with the latest `time` value in order to determine the current value for a Custom Field.
Ideally, we could get a row-based table, like `issue_field_history`, which shows only the latest values so that an increase in the number of Custom Fields in a Jira instance doesn't become a blocker.
This would significantly reduce the amount of data we'd need to process when running queries using Custom Field values.
-
Official comment
Hi Fabio Alves thanks for this suggestion.
I think your suggestion makes a lot of sense. I'm adding to the backlog for now.
-
+1 on this.
In addition, the current Jira ERD and field_option table make it seem like Fivetran is using the soon-to-be deprecated endpoint Get custom field option.
Are there plans to migrate the Fivetran connector to using the new Get custom field options (context) endpoint? -
Adding my interest to this. Also, I've defined a custom field in Jira for RAG status (Red, Amber, Green). I do not see a way to translate the values I get from the connector (numbers) to Red Amber Green text. Any way to do that?
-
We have disabled Jira until this is available
Please sign in to leave a comment.
Comments
4 comments