Stephen Fryer
- Total activity 18
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 4
- Subscriptions 6
Activity overview
Latest activity by Stephen Fryer-
Stephen Fryer created a post,
Connector Improvement: Connector Improvement: Unable to determine if employee is terminated or not
Not plannedRe case 225068 The worker_events table shows Terminated events, but provides no data on whether that termination was subsequently reversed/rescinded. It is critical for a HCM module to be able to i...
-
Stephen Fryer created a post,
Connector Improvement: DEI-related fields missing from Workday HCM connector
PlannedCurrently the Workday HCM connector does not support syncing gender identity and the DEI-related objects like pronoun, sexual orientation. These fields have become critical for businesses to help m...
-
Stephen Fryer created a post,
Connector Improvement: Jira remote linked issues
CompletedFor a particular issue, we wish to track issues linked to it from other Jira instances. The application allows us to do this but these fields are not currently collected by the Fivetran connector.
-
Stephen Fryer created a post,
Connector Improvement: Connector Improvement: Jira knowledge base data
Hi Feature Request Team Please add knowledge base data to the list of Jira fields supported by Fivetran. Thank you! Stephen at Ocado
-
Stephen Fryer commented,
It would be extremely useful for us if this connector was made available. Please consider!
-
Stephen Fryer commented,
Hi Anna Can we progress this feature request, please? Ideally we would like to capture the author id for all field changes. This data is available through the Jira API so Fivetran should be able t...
-
Stephen Fryer commented,
Hi Anna Thanks for the note. I did see this table but our version only has about 600 records in it, so I presumed it was a system table. If you could help me understand how to populate this so a r...
-
Stephen Fryer created a post,
Connector Improvement: Jira user audit detail
CompletedHi - it would be extremely useful to know the last user to update an issue record. The connector pulls timestamps which are obviously critical, but we have no visibility of who created or changed ...