Ketryx can read and display many third-party Jira fields.
However, support for creating or updating these fields depends on how the Jira app implements validation and API behavior.

What happens if a third-party Jira field is required?

If a third-party Jira field is marked as required, Jira may reject create or update requests coming from Ketryx. This can block syncing from Ketryx → Jira, even when the field is mapped correctly.

What options do I have if a required third-party field blocks syncing?

There are two supported approaches, depending on your workflow needs.

Option 1: Keep the field required and allow edit-only behavior in Ketryx

In this setup:

• The third-party field remains required in Jira

• Items must be created in Jira

• Ketryx can sync and edit existing items, except for the required third-party field

• The field is read-only or disabled in Ketryx

Example configuration (Tempo Time Tracking for Jira)

Note:
The following configuration example is specific to the Tempo Time Tracking plugin for Jira.
Other third-party Jira apps may require different configurations and may behave differently.

This example shows how a Tempo-managed Account field can be surfaced in Ketryx in a read-only, sync-from-Jira setup when the field is required in Jira.

Item fields

{
  "Requirement": {
    "addedFields": [
      { "kind": "CUSTOM", "name": "Account" }
    ]
  }
}

Custom fields

{
  "Account": {
    "type": "SHORT_TEXT",
    "isEditableInKetryx": false,
    "syncToExternalSystem": false
  }
}

Jira field mapping

{
  "customfield_XXXXX": "Account"
}

Result

• Jira → Ketryx sync works

• Existing items can be edited in Ketryx

• New items cannot be created in Ketryx when the field is required

Option 2: Make the third-party field optional in Jira

In this setup:

• The field is not required in Jira

• Items can be created directly in Ketryx

• Full Ketryx → Jira syncing works

Result

• Items can be created and synced from Ketryx

• The field can still exist and be used in Jira

• This is the recommended approach when Ketryx creation workflows are needed

Which option should I choose?

• Choose Option 1 if your team primarily creates items in Jira and only edits them in Ketryx

• Choose Option 2 if you want to:

  • Create items in Ketryx

  • Use AI features

  • Import from Excel/Word

  • Create risks directly in Ketryx

Will Ketryx support required third-party fields for creation in the future?

Ketryx continues to evaluate support for additional Jira field types and third-party apps.