Skip to main content
Remote Fields | Ticketing
Updated over a week ago

Introduction

We’re excited to roll out Remote Fields for Ticketing!

This means you can GET & POST Tickets with custom fields.

This is in closed beta, as we aim to ensure the highest quality by investing time & partnering with customers like you.

This means there are features that are not yet supported and are in the works. These are listed below.

What you can do now

Use case

Merge feature

Supported integrations

Get all custom fields metadata

  • GET /tickets/remote-field-classes

Jira, ServiceNow

Get Tickets & their custom fields

  • GET /tickets?include_remote_fields=true

Jira, ServiceNow

Create Tickets with custom fields

  • POST /tickets

  • GET /tickets/:id?include_remote_fields=true

Jira

Examples

  • Get all custom fields metadata

  • Get Tickets & their custom fields

  • Create a Ticket with custom fields

What’s coming up

Use case

Details

Understand what fields are required for a given collection or ticket_type.

We’re currently conducting research, as it varies tremendously across platforms.

Understand what choices are available for a field, taking into account collection or ticket_type.

We’re currently conducting research, as it varies tremendously across platforms.

Custom fields that are relations to other objects, such as Jira versions or ServiceNow users.

We’re in the works of designing a unified experience here.

More integrations!

Next immediately is ServiceNow.

Upcoming are Asana, ClickUp, Zendesk.

FAQ

  • I don’t see all Tickets populated with remote fields. — This could be because the sync is timestamped, so it processes only the latest Tickets. Let us know which linked account you’d like us to force resync from start.

Thank you for partnering with us as we polish your developer experience! Any feedback is absolutely welcome!

Did this answer your question?