Jira

The LILT + Jira integration facilitates efficient communication and project management using your organization's existing Jira project tracker. The integration works by enabling LILT to automatically create new Jira Issues when a new LILT Project is created via another connector (Contentful, Zendesk, etc.) integrated with LILT.

The LILT + Jira integration supports the following:

• Ticket creation: LILT automatically creates a Jira Issue ticket when a new project is created via a connector (Contentful, Zendesk, etc.).

• Ticket properties: The following information will be automatically populated at ticket creation.

  • Project name: Name of project as it appears in LILT.

  • Project link: Links back to the associated project in LILT.

  • Project status: Received or delivered.

  • Documents: List of documents contained in the project.

  • Labels: Apply one or many labels to the Jira ticket.

  • Assign: Ability to assign the ticket to specific Jira users (if desired).

• Task creation: The customer can create tasks within the project for tracking purposes as part of the Linguistic Quality Assurance (LQA) process.

• Reject via Jira: The customer can assign a Jira Issue to LILT to indicate revisions are required.

  • Assign to LILT: The customer can assign a [LILT generated] Jira Issue back to the LILT user, in order to indicate rework is required.

  • Rework notifications: Jira will send an email to the alias associated with the LILT Jira user when a ticket is assigned back to LILT.

Configuration

1. Create a normal user in Jira with your choice of name (for example, LILT).

2. Enable sub-tasks in the Jira project so LILT can create ticket sub-tasks.

3. Contact the LILT Solutions team and provide them with the following information to enable the LILT + Jira integration:

   • Jira username

   • API token

   • Jira server URL

Workflow

Once you have configured your Jira account to work with LILT, you can get to work.

Setup

1. A translation job is created in the connected content management system (CMS) of your choice. For the purposes of this example, we will use Contentful.

2. For each target language in Contentful, LILT creates a corresponding project.

3. Jira creates an Issue Ticket tied to the project.

Translation Flow

Once the project is in place, each selected entry in Contentful will have a corresponding document created in LILT. Subtask Tickets are then created in Jira corresponding to these documents. For example, you would have a LILT project for an English to French translation, a corresponding Jira Issue Ticket for the project, and then for each document in the project, a Subtask Ticket for that document.

The documents are then translated in LILT, and the Subtask's status is updated. It can then be reviewed. If there is any feedback, the Jira status can be updated again, which instructs the LILT Production Manager to unarchive the project and notify the linguist of changes that need to be made. This cycle continues until the document is complete.

Completion

Once there is no more document feedback, the Jira subtask is marked as completed. Once every document subtask has been marked complete, the issue they belong to is marked complete as well. When all issues are marked as completed, the translation job is done.