spec sheet · code & design

Jira and Transglot, turn translation events into issues.

Add your Jira site, credentials, and project key in workspace settings. Choose which project notifications create issues so your team can follow translation work in Jira.

Transglot events → Jira issues

Direction: Transglot events → Jira issues
Plan: Team and up
Scope: issues opened from Transglot events
Authentication: your Jira Cloud site, an account email, an API token and a project key
Get started: Available through the workspace’s Jira Cloud integration.

Create your project Setup

code & design

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect Jira Cloud
Add your Jira Cloud site, account email, API token and project key.
connect
Choose the events
Configure the project events that should create a Jira issue.
events
An event occurs
Transglot emits the configured project notification, such as a translation-batch result.
notify
Open the issue in Jira
Review the created issue in the Jira project you configured.
issue

A project event creates a Jira Cloud issue using the connection and project key you configure.

what moves

What you can translate and deliver.

An actionable event opens one Jira Cloud issue in the project and issue type you pick. It is durable rather than best effort, so a Jira outage retries instead of dropping the work item, and a dedupe key means a retry never opens a second issue.

What you can translate and deliver.
Surface	What to expect
Source and scope	issues opened from Transglot events
Translated output	A project event creates a Jira Cloud issue using the connection and project key you configure.
Keep in mind	This integration creates issues from notifications. It does not import Jira issues as translation content.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

your Jira Cloud site, an account email, an API token and a project key.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Open the workspace’s Jira integration.
Add your Jira Cloud site, account email, API token and project key.
Choose the project notifications that should create Jira issues and save the configuration.

same project, more possibilities