Jira Integration

The Applanga Jira integrations allows you to create Jira tickets from inside Applanga to report translation and localization-related issues into the Jira environment for further handling.

Besides the summary and the description, tickets created via the Jira Integration will carry a link back to the related string keys on Applanga automatically to easily identify where in your app the issue might be located and make us of any context already gathered on Applanaga. For issue reporters, it eliminates the need to work in multiple environments at the same time.

Configuration

The integration works on the Applanga project level, so every Applanga project would need to be connected individually but you can connect multiple Applanga projects to one Jira project. For example, you have multiple apps and every app has its own Applanga project but they are all connected to one project on Jira where translation bug tracking across all apps is unified.

In your Project Settings, go to Jira Integration and click on “Configure”. In the first dialogue, you need to enter your Atlassian host URL which is the general Atlassian subdomain you use and the Jira email address of the user account you want to use. This user account will be the default reporter of all issues created via the Applanga Jira integration.

You can generate a Jira API token by following these steps:

1. Log in to https://id.atlassian.com/manage/api-tokens with the same Jira email you used in the configuration
2. Click Create API token.
3. From the dialog that appears, enter a memorable and concise Label (e.g. Applanga Jira Integration) for your token and click Create.

In the next step of the configuration process, chose the Jira project in which tickets created via the Applanga Jira integration should appear in.

Finally, chose the default issue type which should be preselected for issues created via the Applanga Jira integration, Bug, Story or Task:

Creating Jira Tickets on the Applanga dashboard

To create a Jira ticket, (1) mark all the keys you want to include in your issue report, (2) click on the “More” button at the top of the list and (3) chose “Create Jira Ticket” from the dropdown.

This will create the ticket creation dialogue, where the ticket details can be entered. The summary and the description are mandatory fields. The issue type and the reporter will be preselected as per your Applanga Jira integration configuration.

Working with your Applanga Jira issues

On Applanga, Jira issues behave a lot like tags. You can find all your Jira issues in the tag list. They will get the tag category “Jira” automatically, so if you want to see only your Jira tickets in the list, use the filter on the top right of the tag list and filter for Jira.

On Jira, the ticket will automatically appear in the configured Jira project. Additionally to all the information added to the ticket during the creation process, it will carry an additional sentence in the description field. This additional sentence will contain a link back to the Applanga dashboard with the affected strings already selected.

Creating Jira tickets from inside a mobile app

With the Applanga Jira integration configured, Jira tickets can be created from inside the mobile app during the testing process. The Draft mode includes an additional overlay dialogue to create Jira tickets including an issue title, issue description, a screenshot and a link to the strings on the screenshot on Applanga.

This way, whoever is working with the Jira tickets to resolve the reported issues has a lot of contexts: which part of the app and which strings/string IDs are affected while the process of gathering and reporting this information from the tester’s perspective is much easier compared to the regular way (creating tickets manually)

When the Draft mode is enabled, swipe down with two fingers to activate the capturing overlay whenever you encounter a functional issue that can’t be fixed by simply editing the Draft value(s). Click on Create Issue and add a ticket title and issue description

A Jira ticket created this way will automatically include a screenshot of the affected screen, a link that leads back to Applanga to show all the strings found on the screen.

On Applanga, a tag for the Jira ticket is created, the screenshot is attached to this tag and all strings found on the screen when the ticket was created a tagged accordingly (note: not all strings might be found automatically).