---
title: "BigPicture Localization: Responding to Field Name Translation Queries"
canonical: "https://support.appfire.com/space/SUPPORT/3490382228/BigPicture%20Localization%3A%20Responding%20to%20Field%20Name%20Translation%20Queries"
format: markdown
---
This article helps support agents respond to questions about translating field names such as **Start Date** in BigPicture. Use it when a customer asks whether BigPicture fields or the app UI can be displayed in another language.

> ℹ️ For BigPicture, the application UI is available only in English. If the customer wants field labels in another language, the practical workaround is to translate or rename the underlying Jira custom fields, not the BigPicture UI itself.

# When to use this article

- Customer asks whether BigPicture fields can be translated
- Customer wants labels such as **Start Date**, **End Date**, or similar field names displayed in a non-English language
- Customer is asking about product localization, not a broken display or rendering issue

# Short answer for support

**No, BigPicture Data Center does not currently provide additional UI language variants beyond English.** Field names shown in the app are not translated by a built-in BigPicture localization feature.

If the customer needs field names in another language, suggest these options:

1. Rename or translate the relevant custom fields in Jira
2. Use a browser translation extension as a temporary visual workaround
3. Record the request as product feedback if the customer wants native UI localization

> 📝 Set expectations clearly: there may be feature requests related to localization in the backlog, but support should not promise delivery or timelines.

# Recommended support response

> Thank you for contacting Appfire Support. At the moment, BigPicture for Jira Data Center does not offer additional language versions of the UI beyond English. If you want field names such as “Start Date” to appear in another language, the best available option is to rename or translate those custom fields directly in Jira. Atlassian provides guidance for translating custom fields. As an alternative, you could also use a browser translation tool for on-screen translation. We understand there is interest in native localization, and we can log your feedback for our product team. At this time, we cannot share any implementation timeline.

# Agent guidance

## What to confirm first

- Clarify whether they want to translate a **field label** or the **entire app interface**
- Check whether the field is a Jira custom field surfaced in BigPicture or a native BigPicture UI element

## How to position the answer

- Be direct that BigPicture UI localization is not currently available
- Offer Jira-side field translation as the primary workaround
- Mention browser translation only as a secondary workaround
- If appropriate, attach the customer to an existing feature request or log feedback internally

## What not to say

- Do not promise that localization is coming soon
- Do not imply that support can enable hidden language packs or configuration flags
- Do not frame browser translation as an official product feature

> ℹ️ If the customer specifically mentions French, German, or another language, you can acknowledge that the request is understood and note the language preference when recording feedback.

# Workarounds to share with customers

| Option | When to suggest it | Notes for the agent |
| --- | --- | --- |
| Translate or rename Jira custom fields | Customer wants specific field names shown differently | This is the main workaround. It is the closest match to the request and works best when BigPicture displays Jira-based fields. |
| Browser translation extension | Customer wants a quick visual translation in the browser | This is not a product capability and may produce inconsistent results. |
| Feature request / feedback logging | Customer wants native multilingual UI support | Capture demand, but avoid any commitment on roadmap or timing. |

Useful Atlassian reference: [https://confluence.atlassian.com/adminjiraserver0905/translating-custom-fields-1207177598.html](https://confluence.atlassian.com/adminjiraserver0905/translating-custom-fields-1207177598.html)

# Internal resolution summary

For similar tickets, resolve as [Answered] when the customer has been informed that:

- BigPicture supports English UI only
- Field label translation should be handled on the Jira side where possible
- Browser translation is an optional workaround
- Their localization interest can be captured as feedback