[WEB-3737]chore: updated translations for estimates#6871
[WEB-3737]chore: updated translations for estimates#6871sriramveeraghanta merged 1 commit intopreviewfrom
Conversation
WalkthroughThis pull request updates a wide range of translation strings for estimates and automation features across multiple locales. The strings have been reworded to replace “estimate point” with “estimate” and to improve clarity, consistency, and directness in user messages. Additionally, internationalization has been integrated into the CreateEstimateModal via the useTranslation hook, and the IssueEstimateActivity component now includes type checking and a conversion function for time-based estimates. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant M as CreateEstimateModal
participant T as useTranslation Hook
participant Toast as Toast Service
U->>M: Initiate estimate creation
M->>T: Request localized strings
M->>Toast: Display translated success/error message
Toast-->>U: Show localized toast notification
sequenceDiagram
participant A as IssueEstimateActivity
participant S as ProjectEstimates Store
participant C as Converter (convertMinutesToHoursMinutesString)
A->>S: Retrieve currentActiveEstimate
alt Estimate type is TIME
A->>C: Convert minutes to hours/minutes string
C-->>A: Return formatted value
else
A-->>A: Use raw estimate value
end
A->>U: Render updated estimate information
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Pull Request Linked with Plane Work Items
Comment Automatically Generated by Plane |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (16)
packages/i18n/src/locales/zh-TW/translations.json (9)
1741-1744: Updated "estimates" Terminology
Thelabel,title,description, andno_estimatefields have been updated to use the term “預估”, which is consistent with the new preferred terminology. This change aligns with the overall translation updates across locales.
1746-1750: Revised "create" Sub-section for Estimates
The options under the"create"key now read “自訂”, “從頭開始”, “選擇範本”, “選擇預估系統”, and “輸入預估”. These translations are clear and consistent with the updated terminology. Please verify consistency with similar sections in other locale files.
1755-1762: Updated "Created" Toast Messages for Estimates
The success and error toast messages now read “預估已建立” and “預估建立失敗” with the corresponding messages. These updates provide clear user feedback regarding the creation process. Consider cross-checking with other locales to ensure uniformity.
1766-1772: Updated "Updated" Toast Messages for Estimates
The success and error messages for updating estimates now use “預估已修改” and “預估修改失敗”. The changes enhance clarity for users when an estimate is modified. Consistency with similar messages in related files is recommended.
1776-1777: Revised "Enabled" Toast Message for Estimates
The success message “預估已啟用” correctly reflects the enabled state of estimates. This concise message communicates the status effectively.
1781-1786: Revised "Disabled" Toast Message for Estimates
The "disabled" section now uses “預估已停用” for success and “無法停用預估。請重試” for error, providing clear and direct feedback. This change effectively aligns with the updated terminology.
1791-1798: Enhanced Validation Messages for Estimates
The validation messages now state “預估必須大於0。” for minimum length, and include clear instructions for numeric, character, empty, duplicate, and unsaved changes validations. These improvements enhance clarity and user guidance regarding estimate inputs.
1804-1807: Updated Auto-Archive Automation Translations
The auto-archive section now clearly communicates its functionality with the updated translations: “自動封存已關閉的工作項目” is used consistently for the title, description, and duration. This update should improve the user’s understanding of the feature.
1809-1812: Updated Auto-Close Automation Translations
The auto-close section’s translations have been updated to “自動關閉工作項目” for the title, with corresponding clear descriptions and duration text. This ensures that the feature is easily understood in Traditional Chinese.web/core/components/issues/issue-detail/issue-activity/activity/actions/estimate.tsx (1)
23-29: Added value conversion for time-based estimates.The new
renderValuefunction properly formats time-based estimates into a human-readable format, improving user experience.However, there's a small typo in the variable name:
isTinmeEstimateshould beisTimeEstimate.- const isTinmeEstimate = currentActiveEstimate?.type === EEstimateSystem.TIME; + const isTimeEstimate = currentActiveEstimate?.type === EEstimateSystem.TIME; - if (isTinmeEstimate) { + if (isTimeEstimate) {packages/i18n/src/locales/ko/translations.json (3)
1742-1752: Estimates Section Translation Update
The translations for the estimates section have been updated for clarity and consistency. In particular, the new title ("프로젝트 추정 활성화") and description now use terminology that aligns with the overall language improvements. Under the "create" key, "사용자 지정" replaces the previous term, and "추정 입력" is now used instead of "추정 포인트 입력." Please verify that these changes are harmonized with updates in other locale files.
1786-1788: Toast Messages for Disabling Estimates
The error message for when an estimate cannot be disabled has been revised. While the update is clear, please review the punctuation and overall tone to ensure consistency with similar error messages in the file.
1804-1806: Auto-Archive Terminology Update
In the "auto-archive" automation, notice that the title and description use "완료된" (and also mention "취소된" in the description), whereas the "duration" field uses "닫힌 작업 항목 자동 보관." This slight inconsistency in terminology (완료됨 vs. 닫힘) might confuse users. Please verify whether this is intentional or if the wording should be unified across all keys.packages/i18n/src/locales/en/translations.json (1)
1578-1580: Key Renaming Update: "enter_estimate_point"
The key"enter_estimate_point"has been updated from a phrasing that included “point” to the more succinct and direct"Enter estimate". This update aligns well with the standardized terminology change across the application. Please ensure that similar changes are applied consistently to other locale files.packages/i18n/src/locales/id/translations.json (1)
1789-1797: Validate updated error messages for estimates.
The validation messages have been updated:
• “min_length” now reads “Perkiraan harus lebih besar dari 0.”
• “numeric” and “character” errors specify the expected format.
• Additional messages for unsaved changes and empty values ensure users are informed appropriately.One minor note: The “character” message (“Perkiraan harus berupa nilai karakter.”) could be further clarified to ensure users understand the expected input type if both numeric and character types are allowed in different contexts.
packages/i18n/src/locales/cs/translations.json (1)
1787-1794: Enhance Validation Message Consistency
The validation messages have been updated to standardize the terminology around estimates. Notable changes include:
- “Odhad musí být větší než 0.” for the minimum length requirement
- “Nemůžeme zpracovat váš požadavek, zkuste to prosím znovu.” for general processing failures
- “Odhad musí být číselná hodnota.” and “Odhad musí být znakový.” for type validations
- Additional messages for unsaved changes and empty values have been added for clarity.
Note: Double-check that “znakový” is the desired term in this context; sometimes “textový” might be more conventional when indicating a string input.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (18)
packages/i18n/src/locales/cs/translations.json(2 hunks)packages/i18n/src/locales/de/translations.json(2 hunks)packages/i18n/src/locales/en/translations.json(2 hunks)packages/i18n/src/locales/es/translations.json(1 hunks)packages/i18n/src/locales/fr/translations.json(2 hunks)packages/i18n/src/locales/id/translations.json(3 hunks)packages/i18n/src/locales/it/translations.json(2 hunks)packages/i18n/src/locales/ja/translations.json(2 hunks)packages/i18n/src/locales/ko/translations.json(2 hunks)packages/i18n/src/locales/pl/translations.json(4 hunks)packages/i18n/src/locales/pt-BR/translations.json(2 hunks)packages/i18n/src/locales/ro/translations.json(2 hunks)packages/i18n/src/locales/ru/translations.json(1 hunks)packages/i18n/src/locales/sk/translations.json(1 hunks)packages/i18n/src/locales/ua/translations.json(2 hunks)packages/i18n/src/locales/zh-TW/translations.json(1 hunks)web/core/components/estimates/create/modal.tsx(4 hunks)web/core/components/issues/issue-detail/issue-activity/activity/actions/estimate.tsx(3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Analyze (javascript)
🔇 Additional comments (97)
packages/i18n/src/locales/sk/translations.json (1)
1794-1795: Good addition of new translation keys for estimates.The new translations for "unsaved_changes" and "remove_empty" improve the user experience by providing clear validation messages in Slovak. These keys correspond to the internationalization updates in the CreateEstimateModal component.
web/core/components/estimates/create/modal.tsx (5)
7-7: Good addition of the useTranslation import.Adding the internationalization hook is a positive step toward making the application more accessible to users in different languages.
30-30: Properly initializing the translation hook.The translation hook is correctly initialized, making the
tfunction available throughout the component.
100-102: Success toast messages now properly internationalized.The hardcoded success messages have been replaced with translation keys, improving language support for the application.
108-110: Error toast messages now properly internationalized.The hardcoded error messages have been replaced with translation keys, which will ensure consistent messaging across different languages.
124-125: Validation error message now internationalized.The error message for empty estimate points now uses a translation key, consistent with the new translation entries in the locale files.
packages/i18n/src/locales/ua/translations.json (10)
1717-1717: Updated Estimate Description:
The description for estimates is now “Вони допомагають вам повідомляти про складність та навантаження команди.” This update improves clarity and aligns with the new terminology by removing any outdated wording.
1724-1724: Modified Input Prompt:
The key"enter_estimate_point"has been updated to “Введіть оцінку”, ensuring that the prompt uses the revised term consistent with the overall update.
1729-1730: Updated “Created” Toast Success Message:
The success message in the “created” toast now reads “Оцінку створено” with the accompanying message “Оцінку успішно створено”. This change reinforces the updated estimate terminology.
1733-1734: Updated “Created” Toast Error Message:
The error message has been modified to “Не вдалося створити оцінку”, ensuring consistency with the new naming conventions applied for estimates.
1738-1740: Updated “Updated” Toast Success Message:
The success message for updating an estimate now states “Оцінку змінено” with “Оцінку оновлено у вашому проєкті.” This aligns the update confirmation with the revised translation standards.
1765-1765: Validation - Minimum Length:
The validation message now reads “Оцінка має бути більшою за 0.” This revision simplifies and clarifies the requirement by using the updated term for estimates.
1767-1767: Validation - Unable to Process:
The message “Не вдалося обробити ваш запит, спробуйте ще раз.” has been updated to provide clearer feedback when processing fails.
1768-1768: Validation - Numeric Requirement:
The numeric validation now states “Оцінка має бути числовим значенням.” This makes the requirement explicit using the updated estimate terminology.
1771-1771: Validation - Unsaved Changes:
The message “У вас є незбережені зміни. Збережіть їх перед тим, як натиснути 'готово'” has been refined to clearly instruct users to save changes, consistent with the updated interface language.
1772-1772: Validation - Empty Estimate Handling:
The validation now clarifies with “Оцінка не може бути порожньою. Введіть значення в кожне поле або видаліть ті, для яких у вас немає значень.” This message ensures users understand the input requirements for estimates.packages/i18n/src/locales/ro/translations.json (4)
1741-1742: Updated Estimate Description
The revised description "Te ajută să comunici complexitatea și volumul de muncă al echipei." is now more concise and clear, which aligns well with the updated terminology across locales.
1748-1748: Simplified Input Prompt
The key"enter_estimate_point"now displays "Introdu estimarea" instead of the longer "Introdu punctul de estimare," which improves clarity and consistency with the new naming convention.
1753-1759: Refined Toast Messages for Estimate Actions
Both the success and error messages for the creation and update of estimates have been updated to reflect the new terminology ("Estimare creată," "Modificarea estimării a eșuat," etc.). These messages now offer clear and consistent user feedback.Also applies to: 1763-1769
1789-1797: Enhanced Validation Messages for Estimates
The validation messages now consistently use the term "Estimarea" (e.g., "Estimarea trebuie să fie mai mare decât 0," "Estimarea trebuie să fie o valoare numerică," etc.) and provide clearer instructions. This improves the user guidance on input errors.packages/i18n/src/locales/es/translations.json (6)
1742-1743: Consistency improvement in terminology.The change from "Habilitar estimaciones" to "Activar estimaciones" and the more personalized description with "Te ayudan" instead of just "Ayudan" makes the text more direct and user-friendly.
1750-1751: Simplified terminology from "estimate point" to "estimate".The removal of "point" from "Ingresar estimación" aligns with the broader terminology change across the application, making it more concise.
1755-1757: Streamlined success and error messages for estimates.Replacing "Punto de estimación creado/modificado" with "Estimación creada/modificada" creates a more direct and cohesive user experience, matching the terminology used elsewhere in the application.
Also applies to: 1766-1767, 1769-1771
1776-1787: Improved clarity in enable/disable notification messages.The updated messages for enabling and disabling estimations are more straightforward, which enhances user understanding.
1791-1799: Validation messages aligned with new terminology.All validation messages now consistently use "estimación" instead of "punto de estimación," improving the coherence of the user interface language.
1804-1813: Enhanced clarity for automation feature descriptions.The changes from "Auto-archivar" to "Archivar automáticamente" and similar improvements to the auto-close functionality make these features easier to understand.
web/core/components/issues/issue-detail/issue-activity/activity/actions/estimate.tsx (3)
5-7: Added support for time-based estimate handling.The new imports for
EEstimateSystemenum and time conversion helpers enhance the component's capability to handle different types of estimates.
19-19: Added project estimate context retrieval.Retrieving the current active estimate configuration allows for contextual rendering based on the estimate type being used.
40-41: Simplified activity text and applied value formatting.The simplified text for setting/removing estimates combined with the new value formatting creates a more consistent and user-friendly display of estimate changes.
packages/i18n/src/locales/ko/translations.json (4)
1756-1761: Toast Messages for Estimate Creation
The success and error toast messages for creating estimates have been updated—removing the term “포인트” in favor of a clearer “추정” terminology. This delivers a more consistent user message.
1766-1771: Toast Messages for Estimate Update
The updated toast messages now consistently refer to "추정" (e.g., "추정 수정됨" and corresponding messages). This update helps maintain uniform language across different notifications.
1792-1799: Validation Message Refinements
The validation error messages have been streamlined (e.g., "추정은 0보다 커야 합니다." and "추정 값은 비어있을 수 없습니다.") to be more concise. These improvements should enhance user comprehension when validation errors occur.
1811-1811: Auto-Close Duration Translation
The auto-close duration message ("다음 기간 동안 비활성 작업 항목 자동 닫기") is concise and clear. Confirm that the term "비활성 작업 항목" accurately conveys the intended state of the tasks for this automation.packages/i18n/src/locales/it/translations.json (7)
1739-1740: Updated Estimates Title and Description
The revised title and description now read “Abilita le stime per il mio progetto” and “Ti aiutano a comunicare la complessità e il carico di lavoro del team.” These updates improve grammatical accuracy and clarity within the Italian locale.
1746-1747: Refined Estimate Creation Prompts
The keys have been updated from the previous phraseology to “Scegli un sistema di stima” and “Inserisci stima.” This change streamlines the language by removing redundant wording (e.g. “punto di stima”) and aligning with similar updates across other locales.
1752-1757: Updated Toast Messages for Estimate Creation
The success and error messages for creating estimates have been standardized to “Stima creata” and “Creazione stima fallita” (along with their corresponding messages). This ensures a consistent use of “stima” throughout the interface.
1763-1767: Refined Toast Messages for Estimate Update
The messages for updating estimates now uniformly use “stima” (e.g. “La stima è stata aggiornata nel tuo progetto” and “Modifica stima fallita”). This improves consistency and clarity for end users.
1788-1795: Enhanced Validation Messages for Estimates
The validation messages have been updated to provide more detailed feedback:
- “La stima deve essere maggiore di 0.”
- “Non possiamo elaborare la tua richiesta, riprova.”
- “La stima deve essere un valore numerico.”
- “La stima deve essere un valore di carattere.”
- Plus prompts regarding unsaved changes and removal of empty values.
These updates help users correct their input more effectively.
1799-1803: Improved Automation Labels for Archive Functionality
In the automations section, the label has changed to “Automatizzazioni” and the auto-archive block now features an updated title (“Archivia automaticamente gli elementi di lavoro chiusi”), description, and duration string. These modifications make it clearer that closed work items will be automatically archived.
1808-1809: Refined Auto-Close Duration Message
The auto-close block now uses “Chiudi automaticamente gli elementi di lavoro inattivi per” to describe the duration setting, which clarifies the intended behavior of automatically closing inactive work items.packages/i18n/src/locales/en/translations.json (3)
1582-1591: Translation Update: Estimate Creation Toasts
The success and error messages under the"toasts"→"created"key have been updated to use the new terminology. For example, the success message now reads"Estimate created"with the clear follow-up"The estimate has been created successfully", and the error message has been revised accordingly. These changes improve clarity and consistency in user notifications.
1593-1601: Translation Update: Estimate Modification Toasts
In the"toasts"→"updated"section, the messages now use"Estimate modified"for success and"Estimate modification failed"for error, matching the overall terminology update. This ensures that users receive a consistent message when updating estimates.
1620-1629: Validation Messages Refinement for Estimates
The validation messages under the"validation"key have been revised to remove the redundant “point” reference—for example:
"min_length": "Estimate needs to be greater than 0.""numeric": "Estimate needs to be a numeric value.""character": "Estimate needs to be a character value."- The new
"remove_empty"key clearly instructs:"Estimate can't be empty. Enter a value in each field or remove those you don't have values for."
These updates enhance clarity and align with the new translation standards.packages/i18n/src/locales/fr/translations.json (4)
1741-1749: Estimation Creation Translations Updated
The updated keys such as"no_estimate": "Sans estimation","start_from_scratch": "Commencer depuis zéro", and"enter_estimate_point": "Saisir une estimation"now use the simplified and standardized terminology across the application. These changes improve clarity and consistency compared to the previous “point d'estimation” phrasing.
1751-1769: Toast Messages for Estimate Operations Revised
The toast notifications now consistently use the revised term “estimation” (e.g.,"Estimation créée","Échec de la création de l'estimation", and"L'estimation a été mise à jour dans votre projet."). This update ensures that all user feedback related to estimate operations reflects the new standardized vocabulary.
1789-1797: Validation Messages Enhanced for Estimation Inputs
The validation strings (e.g.,"L'estimation doit être supérieure à 0.","L'estimation doit être une valeur numérique.","La valeur de l'estimation ne peut pas être vide.", etc.) now clearly instruct users using the updated term “estimation.” This change improves both clarity and consistency in user guidance for input validation.
1803-1809: Automation Feature Translations Updated
The description updates for the automation features now reflect clearer language:
"Plane archivera automatiquement les éléments de travail qui ont été complétés ou annulés.""Plane fermera automatiquement les éléments de travail qui n'ont pas été complétés ou annulés."
These changes align the automation messaging with the project’s overall translation improvements. Please verify these descriptions are consistent with similar updates in other locales.packages/i18n/src/locales/pl/translations.json (7)
1718-1719: Translation Update: Revised "description" & "no_estimate" for Estimates
The description now reads "Pomagają w komunikacji o złożoności i obciążeniu zespołu." (instead of using a more cumbersome phrasing) and the "no_estimate" key has been streamlined from "Brak szacunku" to "Bez szacunku" for improved clarity and consistency.
1721-1724: Translation Update: Updated "custom" Label for Estimate Creation
The label for custom estimates has been updated from "Własne" to "Niestandardowy." This improves the precision of the terminology and aligns with similar changes in other locales.
1728-1734: Translation Update: Toast Message for Estimate Creation
The success toast now states "Utworzono szacunek" and the corresponding error title has been updated to "Błąd tworzenia szacunku." These changes standardize the term to "szacunek" across the UI and provide enough clarity to the user regarding the action performed.
1738-1744: Translation Update: Toast Message for Estimate Updates
The update success and error messages now read "Zaktualizowano szacunek" and "Błąd aktualizacji szacunku," respectively. This consistent terminology improves the user experience and matches the language updates made in other parts of the application.
1759-1762: Translation Update: Revised Message for Disabling Estimates
The error message in the disabled state now reads "Nie udało się wyłączyć szacunków. Spróbuj ponownie" to correctly refer to the estimates in plural form. This change ensures semantic accuracy and consistency in the messaging.
1772-1774: Translation Update: Revised Validation Messages for Estimates
The validation messages for unsaved changes ("Masz niezapisane zmiany. Zapisz je przed kliknięciem 'gotowe'") and for empty estimate values ("Szacunek nie może być pusty. Wprowadź wartość w każde pole lub usuń te, dla których nie masz wartości.") have been adjusted for clarity. These messages provide precise guidance and maintain a consistent tone across the interface.
1777-1787: Translation Update: Refined Automations Section in Estimates
The automations section now uses "Automatyzacja" for its label (switching from a possible plural form) and includes updated titles and descriptions for auto-archive and auto-close functionalities. For example, the auto-archive title is now "Automatyczna archiwizacja zamkniętych elementów" with a clear description, and the auto-close section similarly uses "Automatyczne zamykanie elementów" along with an updated status key "auto_close_status" set to "Status automatycznego zamknięcia." These updates enhance consistency and clarity in the feature messaging.packages/i18n/src/locales/id/translations.json (7)
1740-1742: Clarify the 'estimates' description update.
The description has been updated from a plural (“Mereka membantu Anda...”) to a singular and more direct form (“Ini membantu Anda...”). This improves clarity and user focus. Please verify that the language tone matches similar translations in other locales.
1747-1748: Update 'enter_estimate_point' text for consistency.
The key has been changed from “Masukkan poin perkiraan” to “Masukkan perkiraan”, which aligns with the new simplified terminology. This change ensures consistency across translations.
1753-1755: Refine toast message for success on creation.
The updated toast for a successful estimate creation now reads “Perkiraan dibuat” with the message “Perkiraan telah berhasil dibuat”. This removes the redundant “poin” and matches the streamlined terminology.
1757-1759: Update toast message for creation error.
The error toast now reads “Pembuatan perkiraan gagal” and the message “Kami tidak dapat membuat perkiraan baru, silakan coba lagi.” This updated language improves clarity and maintains consistency with the revised terminology.
1763-1764: Confirm update toast message for modifications.
The success message under the “updated” toast now states “Perkiraan telah diperbarui dalam proyek Anda.” This update is clear and consistent with the overall language improvements.
1773-1779: Standardize success titles for activation states.
Both the “enabled” and “disabled” toasts now use a succinct “Berhasil!” title. This uniformity in success messaging is appropriate, but please double-check that the accompanying messages clearly indicate the specific state change.
1802-1810: Review updates to automation translation strings.
Under the “automations” section, both the auto-archive and auto-close keys have been updated:
• The titles and descriptions are now more direct (e.g. “Arsip otomatis item kerja yang ditutup” and “Tutup otomatis item kerja”).
• The “duration” fields and the “auto_close_status” key provide clearer guidance on the automated behavior.These changes improve consistency with the overall language updates. Please verify that these strings align with related translations in other locales.
packages/i18n/src/locales/ja/translations.json (7)
1745-1748: Updated Estimate Creation LabelsThe translation updates in the estimates creation section adjust the wording from using "作成" to "開始" and remove "ポイント" so that "最初から作成" becomes "最初から開始" and "見積もりポイントを入力" is now simplified to "見積もりを入力". This is consistent with the PR objectives and helps improve clarity for users.
1753-1759: Refined Toast Messages for Estimate CreationThe success and error toast messages for creating estimates have been updated to use the simplified term "見積もり" (e.g. "見積もりを作成" and "見積もり作成に失敗") instead of referring to "見積もりポイント". The messages are now clearer and more concise.
1763-1769: Refined Toast Messages for Estimate UpdatesSimilarly, the toast messages for updating estimates have been revised to use the updated terminology. The new language ("見積もりを更新" and corresponding success/error messages) aligns with the overall shift in terminology and improves consistency across the interface.
1783-1785: Clarified Disabled Estimate Error MessageThe error message under the "disabled" block has been updated to:
"見積もりを無効にできませんでした。もう一度お試しください"
This message clearly informs the user and follows the revised language guidelines.
1789-1797: Updated Validation Messages for EstimatesThe validation messages now consistently refer to "見積もり" rather than "見積もりポイント". Changes include:
- Minimum length: "見積もりは0より大きい必要があります。"
- Numeric and character type validations now state: "見積もりは数値である必要があります。" and "見積もりは文字値である必要があります。"
- Additional messages for unsaved changes and non-empty validations have also been updated.
These improvements guarantee consistency across user-facing validation messages.
1803-1805: Updated Automation Text for Auto-ArchiveWithin the "auto-archive" block, the title, description, and duration strings have been revised. The updated texts now clearly communicate that completed or cancelled tasks are archived automatically (e.g. "完了した作業項目を自動的にアーカイブ"). This makes the functionality more intuitive to users.
1808-1810: Updated Automation Text for Auto-CloseThe "auto-close" block has been updated with improved Japanese messages. The revised title ("作業項目を自動的に閉じる") and description now clearly state that non-active tasks are automatically closed, thereby improving overall clarity.
packages/i18n/src/locales/pt-BR/translations.json (5)
1750-1750: Consistent terminology in the estimate prompt.
The key"enter_estimate_point"has been updated to"Inserir estimativa", which removes the redundant “ponto de” prefix. This makes the language more concise and consistent with the overall terminology update across the file.
1755-1757: Standardized success toast for estimate creation.
The success message undertoasts.created.successhas been updated to:
"title": "Estimativa criada""message": "A estimativa foi criada com sucesso"
This clear and consistent phrasing aligns with the new terminology.
1759-1761: Standardized error toast for estimate creation.
The error message undertoasts.created.errornow reads:
"title": "Falha na criação da estimativa""message": "Não foi possível criar a nova estimativa, por favor tente novamente."
This update correctly reflects the terminology change and maintains clarity regarding the error scenario.
1765-1767: Consistent messaging for estimate updates.
The success message for updating an estimate now states:
"A estimativa foi atualizada em seu projeto."
This aligns with the changes made in creation messages and ensures users receive consistent feedback when an estimate is modified.
1791-1798: Refined validation messages for estimates.
The validation block now uses the term “estimativa” consistently across several keys:
"min_length": "A estimativa precisa ser maior que 0.""numeric": "A estimativa precisa ser um valor numérico.""character": "A estimativa precisa ser um valor em caracteres."- Additionally, the newly added
"remove_empty": "A estimativa não pode estar vazia. Insira um valor em cada campo ou remova aqueles para os quais você não tem valores."provides clear guidance when a user leaves the field empty.This cohesive update improves both clarity and consistency.
packages/i18n/src/locales/cs/translations.json (5)
1751-1757: Refine Toast Messages for Estimate Creation
The success and error toast messages for creating an estimate have been updated to use the streamlined term “Odhad.” For example, the success toast now correctly displays “Odhad vytvořen” and “Odhad byl úspěšně vytvořen,” and the error toast provides a more informative message.
1761-1767: Consistent Toast Messages on Estimate Update
The toast messages under the “updated” section now consistently use “Odhad” instead of the previously longer “bod odhadu.” In particular:
- The success message now reads “Odhad byl aktualizován ve vašem projektu.”
- The error title has been changed to “Úprava odhadu selhala” with an accompanying retry message.
These updates enhance consistency across the UI messaging.
1781-1783: Clarify Disable Action Error Message
The error message for when an estimate cannot be disabled now reads “Odhad nemohl být zakázán. Zkuste to prosím znovu.” This update succinctly informs the user of the issue and suggests a retry.
1800-1803: Refine Auto-Archive Automation Text
The automation setting for auto-archiving work items has been updated for better clarity. The title, description, and duration fields now clearly state that the system will automatically archive work items that are completed or canceled.
1805-1809: Refine Auto-Close Automation Text
The auto-close automation translations have been revised as follows:
- The title now reads “Automaticky uzavírat pracovní položky.”
- The description indicates that work items which are not completed or canceled will be automatically closed.
- The duration and auto-close status fields have also been updated to succinctly convey their purpose.
These updates ensure that users understand the automation behavior accurately.packages/i18n/src/locales/ru/translations.json (12)
1741-1741: Refined Estimate Description:
The updated description"Они помогают вам в общении о сложности и рабочей нагрузке команды."improves clarity and focuses on the user by explicitly stating the communication aspect rather than a generic evaluation. Please verify that this phrasing aligns with similar changes across other locales for consistency.
1747-1748: Improved Action Text for Estimates:
The modifications for"choose_estimate_system": "Выбрать систему оценок"and"enter_estimate_point": "Ввести оценку"streamline the language and correct grammatical nuances. These changes make the commands more direct.
1753-1754: Simplified Toast Messaging for Created Estimate (Success):
Changing the toast messages to"Оценка создана"and"Оценка успешно создана"offers a concise and clear confirmation to users. This also aligns with the standardized terminology across the translations.
1757-1758: Clearer Error Toast for Estimate Creation:
The revised error messages"Ошибка создания оценки"and"Не удалось создать новую оценку, пожалуйста, попробуйте снова."remove unnecessary wording and ensure clarity. This update aids users in quickly understanding the issue.
1764-1764: Updated Success Toast for Estimate Update:
The message"Оценка обновлена в вашем проекте."is succinct and communicates the successful update without excess verbiage. This is a solid change for user feedback.
1768-1768: Revised Error Toast for Estimate Update:
The updated error description"Не удалось изменить оценку, пожалуйста, попробуйте снова"clearly instructs users on a retry, maintaining a consistent tone with other feedback messages.
1773-1773: Enabled Toast for Estimates:
The enabled toast now uses"Успех!"along with"Оценки включены."—this concise messaging is effective and matches other affirmative feedback in the system.
1779-1784: Disabled Toast for Estimates:
The changes for the disabled state—updating the title to"Успех!"and the error message to"Не удалось отключить оценки. Пожалуйста, попробуйте снова"—ensure the messaging is clear and consistent with the rest of the interface. Consider a quick review to verify that the tone is uniform with similar alerts elsewhere in the project.
1789-1797: Enhanced Validation Messages for Estimates:
The revised validation messages now provide clearer guidance:
"Оценка должна быть больше 0.""Не удалось обработать ваш запрос, пожалуйста, попробуйте снова.""Оценка должна быть числовым значением.""Оценка должна быть символьным значением."- Additionally, messages for duplicates and unsaved changes (
"Значение оценки уже существует.","У вас есть несохраненные изменения. Пожалуйста, сохраните их перед нажатием на готово", and"Оценка не может быть пустой. Введите значение в каждое поле или удалите те, для которых у вас нет значений.") enhance user clarity and provide specific actionable feedback.
1803-1804: Improved Auto-Archive Descriptions:
The updates in the auto-archive section clarify the functionality: the description now reads
"Plane будет автоматически архивировать рабочие элементы, которые были завершены или отменены."
and provides precise information on the duration with
"Автоархивация рабочих элементов, которые закрыты в течение".
These changes make the behavior more transparent to users.
1807-1810: Revised Auto-Close Messaging:
The auto-close functionality now features updated text:
- Title:
"Автоматическое закрытие рабочих элементов"- Description:
"Plane будет автоматически закрывать рабочие элементы, которые не были завершены или отменены."- Duration and additional status information are now specified, offering users more insight into how inactivity is determined.
1820-1822: Clarified Empty State for Estimates:
Updating the empty state to
"title": "Нет систем оценок""description": "Создайте набор оценок для передачи объема работы на каждый рабочий элемент.""primary_button": "Добавить систему оценок"
provides explicit instructions to users on the next steps when no estimate system is defined. This clarity will improve user navigation in the feature.packages/i18n/src/locales/de/translations.json (7)
1715-1715: Personalized Estimate Description Updated
The description string for estimates has been updated from a generic phrasing to a more direct, personalized tone (“Sie helfen dir, die Komplexität und Arbeitsbelastung des Teams zu kommunizieren.”). This strengthens the user engagement and aligns with the overall translation improvements.
1719-1722: Consistent Update of Creation Labels for Estimates
The update in the "create" section replaces the previous “Schätzungspunkt eingeben” and similar phrases with clearer terms:
- "Von Grund auf neu" instead of a less precise phrase
- "Vorlage wählen" for template selection
- "Schätzungssystem wählen" clarifies the system choice
- "Schätzung eingeben" simplifies the input prompt
These changes are consistent with the PR objective to update translations for estimates, ensuring clarity and brevity.
1727-1733: Refined Toast Messages for Estimate Creation
The toast messages under the “created” section now use updated wording such as “Schätzung erstellt” and “Die Schätzung wurde erfolgreich erstellt” for success, along with improved error messaging (“Schätzungserstellung fehlgeschlagen” and “Wir konnten die neue Schätzung nicht erstellen, bitte versuche es erneut.”). This improves user clarity and integrates smoothly with the new tone across the translations.
1736-1743: Enhanced Toast Messages for Estimate Updates
The updated messages for estimate updates now read “Die Schätzung wurde in deinem Projekt aktualisiert.” for success and “Schätzungsänderung fehlgeschlagen” with the corresponding error message for failure. These translations adopt a more conversational tone by using “deinem Projekt” and maintain consistency with other estimate-related texts.
1756-1758: Clarification in Disabled Estimate Toast Messaging
The disabled toast now states “Schätzung konnte nicht deaktiviert werden. Bitte versuche es erneut”, which is concise and clear. This minor change complements the overall update in tone for estimate-related notifications.
1763-1770: Detailed and Consistent Validation Messages for Estimates
The validation messages for estimates have been comprehensively updated to cover multiple scenarios:
- Enforcement of a minimum value (“Die Schätzung muss größer als 0 sein.”)
- Handling of processing failures, type checks (numeric and character), empty inputs, duplicate values, and unsaved changes.
These messages now provide specific, instructive feedback to the user, ensuring consistency with the clear language updates across the file.
1774-1784: Updated Automation Translations for Estimate Features
The translations within the “automations” block now reflect the new tone:
- The label is updated to “Automatisierungen”.
- Under “auto-archive”, the title and description are now more explicit.
- Likewise, the “auto-close” section provides updated text for title, description, duration, and status.
These changes maintain consistency with the overall update for estimates, ensuring that all related UI notifications are communicated clearly.
3 participants
Description
Updated translations for estimates.
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
WEB-3737
Summary by CodeRabbit