Bug Assignment

General Rules

Create bugs for all issues found into our bug tracker – 🔗Bugnet. The main purpose of bugs in Bugnet is to let our translators know how to fix the issues while translating.

For the issues which can't be fixed during translation (e.g. truncation, number/date format issue), these bugs are usually assigned to Tableau (via their own bug database called GUS) for further investigation. These bugs are set by our engineers during ENG QA to the following status in Bugnet:

Assigned to: Tableau Technical Issue
Status: opened
Resolution: -- Select Resolution --

Please do not report issues with SKIPPED as a test result. There are also some general rules that should be followed when deciding what and how to fill in Bugnet – please see below.

There are sequences of screenshots that are captured in the same dialog window – please do not create duplicate bugs reporting the same thing, but rather file only one global issue.
Report only one issue per bug ID.
Make sure that the bug in Bugnet contains as much information as possible for our translators to be able to fix them.
lease be aware that content from data files explained above should not be reported as bugs (ex. workgroups, users, projects, workbooks).
If the date format is wrong, please choose the appropriate failure reason, but don’t report it as bug in Bugnet as this cannot be fixed by our translators.
If screenshots do not match, or there are differences, please don’t create a bug in Bugnet either, but only choose the correct failure reason for that given screenshot and specify by a comment.
Please be extra careful while reporting issues about incorrect translations, some terms are already approved by the client or have been used for a long time. You have to check a 🔗Tableau term base in Kalcium before suggesting term changes.
If the issue is related to any high impact term changes, we need to discuss with Tableau team first to decide timing/scope. Please do not log these issues in Bugnet. Instead, please notify us about your suggestion via email. This instruction applies to:

o High visibility terms (Used in UI)

o High impact terms (Used in many places in files)

Bugnet

There are several mandatory fields that need to be filled in in order to properly assign a bug. Please see below the information about bug template which should be used when performing this work.

A. Bug ID

Before saving the bug, you will see Issue: N/A value in the record header.
This will be changed to number value once saved.

B. Bug Title

Title: [CLT type: Product name:ll-CC] title with a short description

- CLT type – There are usually 2 types of CLT test drops:
  - CLT-Main
  - CLT-Misc
- Product name – we test the following products:

o CLT-Main Products:

§ Tableau Desktop

§ Tableau Server

o CLT-Misc Products:

§ Tableau Mobile iOS

§ Tableau Mobile Android

§ Tableau Prep

💡 The product name can be identified from the zip files in the HO packages:

ll-CC - stands for a locale and culture code of each particular language (e.g. en-GB, pt-BR, es-ES, zh-CN, it-IT, etc.). Please choose the one you’re assigned to.
Bug title examples:

o [CLT-Main:Desktop:zh-TW] Incorrect Translation

o [CLT-Misc:Prep:fr-FR] Truncation

o [CLT-Main:Server:de-DE] Missing period

o [CLT-Misc: Mobile iOS:ko-KR] Consistency issue

o [CLT-Misc: Android iOS:es-ES] Mistranslation

C. Source and Target String

In case the testing issue is related to specific text please rewrite the Source and Target sentence into the specific fields in Bugnet. This will help the translator to identify the exact correction need.

D. Filename

Filename field should contain the full name of a screenshot which contains the issue you’re reporting.

Please use full name as provided in bug report (e.g. Additional Test Cases Request_1.PNG) as this value is used in other process steps.

E. Component, Project, Subproject and Handoff

Component field will be “UI-Memsource (Phrase)” for your testing task.

Project / Subproject / Handoff: can be skipped

F. Type, Priority, Assignment and Status

Type: select the type which best describes the bug (usually it is “Localizable issue”)

Priority: Priority is always going to be “1”

Assigned to: Please always assign the bug to JTE_ENG account so our engineer can validate all reported issues. (📌 Important: do not leave this assigned to yourself!)

Status: Please always set the status to “opened” when creating a new issue

Resolution in this case remains greyed out.

G. Language and other fields

Language: Self-explanatory – this will always be your assigned language

Resource ID/Topic / Bug In Source / Due Date / Percent Complete / Estimation: ignore

H. Description

Description of the issue: If there’s incorrect or missing translation in target, please also include the below in the Description:

Affected English string:
Current translation:
Expected translation:

📌 Please try to be descriptive in this field so translator will be able to easily understand the correction need.

I. Attachment

Please always attach corresponding screenshot/s with the actual issue(-s) highlighted on the screenshot, showing both English and target version. Otherwise, the bug will be assigned back to you, and you will be asked to attach it. Our engineers and linguists need to see the issue in the full context of the UI like you do to agree with the suggested change.

Examples of screenshots showing the issues correctly:

Also in Attachment filed please use the correct name of the screenshot:

Report – finalization

Please note that all of the issues you reported in Bugnet were assigned IDs upon creation. These Bug IDs need to be inserted into the bug report in column G.

If the test result is ‘PASS’, or ‘SKIPPED’, this cell will remain empty.