Update translations.ts: issue-artifacts discovered

[conny3496]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• Localization
  • Updated terminology in workspace analytics empty state messaging to consistently refer to "work items" instead of "issues."

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

Updated translation strings in the English locale configuration, changing terminology from "issues" to "work items" in the workspace analytics empty state messaging related to timeboxing and grouping functionality.

Changes

Cohort / File(s)	Summary
i18n Translation Update packages/i18n/src/locales/en/translations.ts	Replaced "issues" with "work items" in the workspace analytics no-data state description for primary button text

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop through translations, terminology refined,
"Work items" now gleam where "issues" used to mind,
In empty states we whisper true,
Fresh words for workspace views, renewed and bright as dew. 🌿

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is largely incomplete. While the template structure is present and "Code refactoring" is checked in the Type of Change section, all other critical sections remain empty or only contain template comments. The Description section, which should provide detailed information about the changes, is blank. Similarly, Test Scenarios and References sections are missing, providing no context about how these translation changes were tested or validated. The absence of a substantive description makes it difficult for reviewers to understand the rationale and scope of the translation update.	Complete the pull request description by filling in the Description section with details about why the translation was updated from "issues" to "work items," add Test Scenarios explaining how the translation changes were verified, and include any relevant References or issue links. This will provide reviewers with sufficient context to understand and evaluate the changes effectively.
Title Check	❓ Inconclusive	The PR title "Update translations.ts: issue-artifacts discovered" is vague and unclear. The phrase "issue-artifacts discovered" does not convey meaningful information about the actual change, which according to the raw_summary is a text update in a translation file where "issues" was replaced with "work items" in a workspace analytics empty state message. The title uses non-descriptive terminology that does not accurately reflect what was changed or why, making it difficult for someone scanning the repository history to understand the purpose of this commit.	Consider revising the title to be more descriptive and specific, such as "Update translations: change 'issues' to 'work items' in workspace analytics" or similar. This would clearly communicate the nature and scope of the translation change to reviewers and future developers reviewing the repository history.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 f266cd8 and 87801b2.

📒 Files selected for processing (1)

• packages/i18n/src/locales/en/translations.ts (1 hunks)

🔇 Additional comments (1)

packages/i18n/src/locales/en/translations.ts (1)

1237-1237: LGTM! Terminology consistency improvement.

The change from "issues" to "work items" aligns with the consistent terminology used throughout this translations file and improves the user experience.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[conny3496]

Was originally looking to improve on this:

...but it turns out that it is already fixed in the Cloud-Version and it only shows like that on my/our local instance. Found the other artifacts while double-checking.