chore: update russian translation

[ch4og]

Description

Updated the Russian translation to correct inconsistencies caused by #6672 and #6666

It used the same word for both 'inbox' and 'intake.' Since there is no direct translation for 'intake' in Russian, I translated it as proposals/offers. Please let me know if this translation doesn't suit the project.

Also renamed "Issues" to "Work items"

Type of Change

• Improvement

Summary by CodeRabbit

• Documentation
  • Refined Russian UI text for improved clarity and consistency. Key updates include:
    • Replacing "task" with "рабочий элемент" (work item) across various contexts.
    • Updating the term for "workspace" to "Рабочие пространства."
    • Enhancing password strength messages for clarity.
    • Adjusting project management and notification phrases for consistency.

[coderabbitai]

Walkthrough

The changes update the Russian locale translation file, specifically the translations.json. The term "task" has been replaced with "рабочий элемент" (work item) for consistency, and other phrases have been adjusted accordingly. The translation for "workspace" has been updated to "Рабочие пространства," and password strength indicators have been refined. These updates aim to standardize terminology throughout the application.

Changes

File Path	Change Summary
packages/i18n/.../ru/translations.json	Updated Russian translations: replaced "task" with "рабочий элемент," changed "workspace" to "Рабочие пространства," and refined password strength indicators.

Possibly related PRs

• feat: russian translation #6666: The changes in the main PR, which focus on updating translation strings in the Russian locale, are directly related to modifications that enable the application to import these Russian translations from the same translations.json file.

Suggested reviewers

• anmolsinghbhatia
• sriramveeraghanta

Poem

In a code burrow, I hop with cheer,
Revising words so all are clear,
From "task" to "рабочий элемент" bright,
My little paws bring language to light,
Carrots and code, a delight so dear!
🐇💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 68fd3b6 and 41b1b4e.

📒 Files selected for processing (1)

• packages/i18n/src/locales/ru/translations.json (50 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

🔇 Additional comments (20)

packages/i18n/src/locales/ru/translations.json (20)

5-15: Sidebar Terminology Update: Consistency in Menu Labels

The updated keys in the sidebar—namely:

• "new_work_item": "Новый рабочий элемент"
• "work_items": "Рабочие элементы"
• "intake": "Предложения"
• and the updated "workspace": "Рабочие пространства"

—reflect the intended terminology shift (from “задача”/ambiguous terms to “рабочий элемент” for work items, and a clarified translation for intake as “Предложения”). Please verify that these terms are now consistently used across all related modules.

---

57-58: Password Strength Indicator Translation

The strings for password strength:

• "weak": "Слабый пароль"
• "strong": "Сильный пароль"

are clear and concise. They fit the overall tone of the UI and match the project’s terminology standards.

---

85-86: "New to Plane" & "Back to Sign In" Label Updates

The updated translations:

• "new_to_plane": "Впервые в Plane?"
• "back_to_sign_in": "Вернуться к входу"

set an inviting tone while keeping the language consistent. Confirm that this friendly tone aligns with the rest of the application.

---

145-145: Password Reset Instruction Clarity

The updated message:
"Проверьте ваши входящие для ссылки на сброс пароля. Если она не появится в течение нескольких минут, проверьте папку спама."
provides clear, actionable guidance for users. The language is both instructive and empathetic.

---

578-588: Recents and Quick Links Update

The revised text for recents and quick links now uses the term “рабочие элементы” (e.g. "issue": "Недавние рабочие элементы появятся здесь после посещения.") to reflect the updated terminology. This change improves clarity and ensures consistency in how work items are referenced across the platform.

---

363-369: Workspace Descriptions and Labels Consistency

Changes in this block update several keys such as:

• "intake": "Предложения"
• "work_management": "Управление рабочими элементами"
• "projects_and_issues": "Проекты и рабочие элементы"
• "cycles_description": "Группировка рабочих элементов по временным интервалам с возможностью изменения периодичности."

These modifications align the language with the new standard. Please double-check that similar phrases in other parts of the application use the same vocabulary.

---

409-427: Issue Creation and Duplicate Detection Terminology

Within the issue-related keys, the translations have been updated to replace previous terms (like “задача”) with “рабочий элемент.” For example:

• "issue_created_successfully": "Рабочий элемент успешно создан"
• "issue_creation_failed": "Ошибка создания рабочего элемента"
• "duplicate_issue_found": "Найден дублирующийся рабочий элемент"

This change is crucial for consistency across the UI. Please verify that all areas where tasks are mentioned now reflect this unified terminology.

---

662-665: Standardizing Task Terminology Across Components

The keys for both singular and plural forms have been updated:

• "work_item": "Рабочий элемент"
• "task": "Рабочий элемент" and "tasks": "Рабочие элементы"

This update resolves previous inconsistencies. It’s important to ensure that every component referencing tasks reflects this uniform naming convention.

Also applies to: 836-837

---

1032-1035: Issue Detail Section Update

The descriptions for non-existent or deleted work items now read:

• "title": "Рабочий элемент не существует"
• "description": "Данный рабочий элемент был удален, архивирован или не существует."
• The call-to-action now reads: "Посмотреть другие рабочие элементы"

These changes improve clarity for end users when an issue cannot be found.

---

1040-1040: Sibling Work Items Label

The updated label "Связанные рабочие элементы" effectively communicates the relationship among work items.

---

1071-1073: Deletion Action Label Update

Changing the deletion label to "Удалить рабочий элемент" is a welcome update that solidifies the consistent use of terminology when referring to work items.

---

1076-1078: Subscription Action Text Update

The messages for subscription actions:

• "Подписка на рабочий элемент оформлена"
• "Подписка на рабочий элемент отменена"

confirm that users receive clear, consistent feedback about their subscription status regarding work items.

---

1081-1085: Select and Full Screen Actions

The updated error message "Выберите хотя бы один рабочий элемент" and the full screen instruction "Открыть рабочий элемент в полном экране" ensure that interactive elements adhere to the new naming conventions.

---

1188-1188: Inbox Issue Creation Label

The label "Создать входящий рабочий элемент" clearly denotes the nature of the work item, particularly when differentiating incoming requests.

---

2158-2174: Draft Work Item Section Update

The key "draft_an_issue": "Создать черновик рабочего элемента" along with its description now unambiguously tells users that drafts pertain to work items. The friendly tone (including the 😉 emoji) is a nice touch, but please verify that this style is acceptable throughout the project.

---

2269-2270: GitHub Importer Description

The GitHub importer now reads:
"description": "Импорт рабочих элементов из репозиториев GitHub с синхронизацией."
This concisely explains the functionality. Confirm that the description aligns with user expectations and documentation.

---

2274-2275: Jira Importer Description

The updated Jira importer description:
"description": "Импорт рабочих элементов и эпиков из проектов Jira."
provides clarity on the scope of imported data. No further adjustments needed unless the integration specifics change.

---

2281-2298: Exporters Section Consistency

For the exporters (CSV, Excel, JSON), the descriptions now uniformly reference “рабочих элементов.” This ensures that end users clearly understand what data is being exported. Double-check that the technical details (such as file formats) remain accurate.

---

2301-2304: Default Global View Label Updates

The default view options now use:

• "all_issues": "Все рабочие элементы"
• "created": "Созданные"
• "subscribed": "Подписанные"

These concise labels reinforce the new terminology. Confirm that they work well in the UI layout.

---

2332-2332: Project Modules Section Terminology

The update to keys such as "planned": "Запланировано" and "issues": "Количество рабочих элементов" further integrates the revised language into project management views. Ensure that these changes harmonize with other project-related labels.

Also applies to: 2346-2346

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.