Bug fixing

Overview

Bug fixing is the process where we fix all issues during translation or engineering postprocessing. All the bugs which can't be fixed in files for translation  are addressed to customer's development team for correction in code. Bugs are managed via 🔗Mantis.

There are various sources of bugs in Tableau localization:

• Functional Linguistic Testing (➡️FLT)

• Contextual Linguistic Testing (➡️CLT)

• Bugs reported in customer feedback (they contain "GUSID:" in the title; GUS is Tableau's bug database and "GUSID" helps us to provide a connection between Mantis and GUS)

• Terminology updates

• LQA implementation requests

• etc...

Bug Assignment

Based on the actual status of a bug, it can be assigned to different roles:

• Linguist (Jonckers_XYZ) - Bug's status is set to "opened" and is assigned to a linguist for fixing in a translatable text

• Tester (JTE_TEST_XYZ) - Bug from FLT/CLT is returned to a Tester for review in a new testing round

• Acclaro's Project Manager / Engineer (JTE_PM, JTE_ENG) - Bug is assigned to Acclaro for revision or investigation

• Customer (Tableau Technical Issues) - Bug is addressed to customer for investigation

Bug Fixing process

1. Bug is raised in Mantis.

2. Bug is reviewed by Acclaro to ensure correct assignment to a proper role.

3. Bug follow-up:

   • Assigned to Linguist - Linguist needs to review the requested fix in the current UI or UA project (depending on a component reported in the Bug). Once corrected in the UI/UA files, the bug is assigned back to JTE_ENG for review, with status leaving as "opened". After it is reviewed by Acclaro's engineer (JTE_ENG), the bug is assigned back to its creator (e.g. Tester, Customer...) for confirmation and closing, if everything is verified as fixed. A linguist has the right to reject the suggested change if it is not in line with the TB or if it would create further inconsistency/style issues. (a note why must be provided in Mantis)

   • Assigned to Tester - Bug is assigned back to a tester in case it is considered as resolved. Bug can be resolved in various scenarios (Fixed, By Design... for more information see  ➡️Bug Resolution page). Once the bug is confirmed as resolved by tester, the tester changes its status from "resolved" to "closed". If the bug is not yet resolved in a current CLT round, the bug is assigned back to JTE_ENG for review. Recognition of bug resolution could take more than one CLT round depending on implementations in SW builds by the customer.

Bug fixing workflow in detail

1. Search for bugs assigned to your profile (an example Jonckers_KOR1). You can see the issues on View Issues tab.

2. Open the bug, check the description and comments section.

Other

For more information about bugs, please refer to:

• ➡️Bug Assignment for new bug creation

• ➡️Bug Resolution for follow up on the existing bugs

• ➡️Tools for information about Mantis