Connector Improvement: Support for Secure Fields in Jira
Not plannedCurrently, Fivetran supports only changes that are represented in the changelog/history section of an issue. Those changes are then populated to issue_field_history and/or issue_multiselect_history. Our customer created a custom field through a Jira extension called Secure Fields, and while the field is captured in issue_field_history, the timestamp as well as author_id are incorrect - the timestamp corresponds with the ticket creation date and author_id corresponds with the author of the ticket. The expectation is that both the timestamp and author_id would show the correct that of when the field was enabled and who made the change. Fivetran support let us know that the historical data needs to be shown in the changelog of an issue so fields created by addons are not supported. This is a high priority for our customer who wanted to receive a timeline if the feature request is accepted by Fivetran.
This was discussed in ticket 178082.
-
Official comment
Hi Monika,
Thank you for submitting this feature request. At this time, support for secure fields in Jira created by extensions such as Secure Fields is not on our current roadmap as API support for plugins is limited. We will re-evaluate if new updates to the API are made.
Thanks,
Frank -
Hi Monika,
Thanks for raising this request. I will add it to the backlog for our team to look into this.
Best,
Frank
Please sign in to leave a comment.
Comments
2 comments