Connect Jira
Open a Jira Cloud issue automatically whenever something in transglot needs a person to act.
The Jira integration turns transglot's actionable events into Jira Cloud issues, one issue per event, in the project and issue type you choose. It is one-way: transglot writes to Jira and never reads from it, so your team can triage, move or close the issues without changing anything in transglot.
Requirements
- Plan: Team or above. On a lower plan the Jira card offers Upgrade plan instead of Connect.
- Role: Admin of the workspace, or an Owner of its account. Other members can open the Jira page and see whether it is connected, but not change it.
- In Jira: a Jira Cloud site, an Atlassian account that can create issues in the target project, and an API token for that account.
Connect Jira
Create an API token
Sign in to Atlassian as the account transglot should act as, then go to id.atlassian.com, Security, API tokens and create a token. Copy it: Atlassian shows it once.
Open the Jira page
In your workspace, open Integrations and select Connect on the Jira card.
Fill in the connection
| Field | What to enter |
|---|---|
| Jira site URL | Your site address, for example https://your-team.atlassian.net |
| Atlassian account email | The email of the account that owns the API token |
| API token | The token you created. It is stored encrypted and never shown again |
| Project key | The key of the Jira project issues should open in, for example LOC |
| Issue type | The issue type to create. Leave it as Task unless your project uses another type |
Save
Select Connect. The confirmation reads "Jira connected." and the Jira card on the integrations page now shows connected.
What opens an issue
transglot opens one issue each time one of these happens in the workspace:
- A review is requested.
- A source drift is repaired.
- An assignment is created, or sent back for changes.
- A translation batch fails, or finishes with some strings left untranslated.
Comments, mentions and completed batches never open an issue, so the Jira project stays a list of things that need somebody. Each event opens its own issue: two failed batches produce two issues. Issue titles and descriptions are written in English and link back to the place in transglot where the work is.
Change or disconnect
To change the project, issue type or account, open the Jira page, edit the fields and select Save. Leave API token blank to keep the stored token.
To stop opening issues, select Disconnect and confirm Disconnect Jira?. Issues already created stay in Jira with their links back to transglot.
Troubleshooting
The first connection needs a token. Paste the API token into API token and save again.
Check that the Atlassian account whose token you used can create issues in that project, that the Project key is the project's key (not its name), and that the Issue type exists in that project. Remember that only the events listed above open issues.
Jira is included on the Team plan and above. See Plan requirements.
Related
Zapier, Make and n8n
Start an automation when something happens in a transglot project, and drive transglot from your flows over the API.
Import from another localization tool
Bring a project's keys and existing translations across from Lokalise, Phrase, Crowdin, Transifex, Weblate or POEditor in one run.