The Lionbridge JIRA vendor portal is a special portal for Lionbridge (https://www.lionbridge.com) handling only the jobs of one Lionbridge technology customer. There is only one instance of this system running. We recommend that you set up the Auto-approve functionality for Lionbridge's portals, because they mostly work on a first come-first served basis.

Use cases:

BeLazy supports integration with Lionbridge JIRA through a specialized connector that enables seamless issue management. The main use cases where the JIRA integration is valuable:

  • You need to handle new issues and LQE issues from Lionbridge's technology customer
  • You want automatic issue acceptance and tracking for first come-first served assignments
  • You need to synchronize JIRA issue details with your business management system or tracker
  • You want to track work completion through the Polyglot system without manual delivery requirements

Integration type:

The Lionbridge JIRA integration uses a mixture of internal APIs and the public JIRA APIs to connect to this highly customized JIRA instance. We also use some web scraping where necessary. This hybrid approach provides comprehensive access to both standard JIRA functionality and Lionbridge-specific customizations.

Requirements:

There are no requirements to use the Lionbridge JIRA portal other than having a valid username and password. To use the Lionbridge JIRA vendor portal, you will only need the URL, user name, password that you use on the portal.

 

Expected URL format:

The URL is always https://aps.lionbridge.com/
 

Lionbridge JIRA-specific configuration:


The Lionbridge JIRA integration has several connector-specific configuration options:

  • Jira board specification: You have to specify the Jira board from where BeLazy will download the issues. Once you are logged in to Lionbridge Jira, select the appropriate board and copy-paste the board's URL from the browser (e.g., https://aps.lionbridge.com/secure/RapidBoard.jspa?rapidView=<ID>).
  • Use custom weights: Lionbridge Jira provides the overall weighted quantity, but not the weights for the individual analysis categories. If you check this checkbox you can fill in the weights that you work with, otherwise the analysis will be ignored by BeLazy.
  • Analysis weights configuration:When custom weights are enabled, you can configure weights for different analysis categories:
    • Translated (100%)
    • Context match (95-99%)
    • Repetitions (85-94%)
    • Format change (75-84%)
    • No match (50-74%)
    • MT (Machine Translation)
  • Issue statuses to sync: Here you can select statuses that BeLazy will pick up during synchronization along with LQE issues. Available statuses include New, Waiting for assignment, and In progress.


Functionalities and connector-specific information:

  • Unit of acceptance: Issue or SubIssue
  • Multiple target languages: Supported through bundling
  • Issue types: New issues and LQE issues are automatically displayed - translation tasks, packages and Dropbox translation tasks are all supported
  • Pricing: Pricing is not extracted from JIRA - only match rates and weights are available. Actual prices come from the business management system or tracker
  • Project exclusion: Not supported
  • Download files: Not supported - this system does not work with files at all
  • Delivery: Not required - projects automatically close when vendor performs work in Polyglot
  • Manual delivery detection: Supported - projects automatically close when vendor performs work in Polyglot
  • Linguist assignment: Not supported - JIRA portal does not support this functionality
  • Project bundling: Supported
  • 2-factor authentication: Not supported
  • Data synchronization: Issue details and status updates are synchronized with configurable status filtering


Typical issues and how to resolve them:

  • Board configuration: Ensure you specify the correct Jira board URL during setup. The URL format should be https://aps.lionbridge.com/secure/RapidBoard.jspa?rapidView=<ID>. If issues are not appearing, verify that you have access to the specified board and that the URL is correctly copied from your browser.
  • Analysis weights setup: If you need pricing calculations based on analysis categories, enable "Use custom weights" and configure the weights for each category (Translated, Context match, Repetitions, Format change, No match, MT). Without this configuration, analysis data will be ignored by BeLazy.
  • Status synchronization: Configure the appropriate issue statuses (New, Waiting for assignment, In progress) in the "Issue statuses to sync" section to ensure BeLazy picks up the relevant issues during synchronization.
  • Project bundling and workflow structure: Each workflow in JIRA is single-step. You can use the job bundling to turn consecutive steps such as translation, revision into one workflow in your business management system or tracker. Daily and monthly project bundling and project bundling creating one project with different language pairs are supported.
  • Instruction mapping: All instructions are extracted from the various instruction fields in JIRA, and can be automatically reused in your customizable, client and program-specific instructions to the project managers and the vendors.
  • Synchronization: By default, the connector is synchronized every 30 minutes, but you can also synchronize immediately once an email with a new job offer comes in.


Connector-specific data extracted: See here.