Custom Nomenclature issues overview¶

This page is a quietly on-going background WIP effort. Please be aware that the information provided on this page may be out of date, or otherwise inaccurate.

---

• Table of contents
• Custom Nomenclature issues overview
  • Introduction
  • Summary
  • Forms
  • Issue and reference list
    • T9n level
    • I18n level
    • Conceptual level

Introduction¶

This page lists an overview of open and closed issues which are speaking specifically about custom nomenclature in several ways. This list could be used while managing all the issue relations.

Summary¶

Current	Some alternatives
tracker	type, kind, variety, class, category, classification, group, set, genre, genus, species, family, order, breed, race, strain, etc.
issue	task, ticket, work item, work package, case, order, request, demand, item, etc.
version	milestone, target, phase, stage, iteration, sprint, collection, deliverable, etc.
[parent|sub] task	[parent|sub] issue, ticket, work item, work package, case, order, request, demand, item, etc.
[issue] subject	[issue] title
private	restricted, confidential, embargo
status	phase, stage, period, chapter, episode, part, step, etc.
% done	progress, progression
roadmap	planning, schedule
project	department, unit
watch[er]	follow[er]
news	blog
activity	activity

Forms¶

Forms	Example 'issue'	Example 'version'
singular-lowercase	issue	version
plural-lowercase	issues	versions
singular-capitalized	Issue	Version
plural-capitalized	Issues	Versions
singular-with-indefinite-article-lowercase	an issue	a version
plural-with-indefinite-article-lowercase	-	-
singular-with-indefinite-article-capitalized	An issue	A version
plural-with-indefinite-article-not-capitalized	-	-

Issue and reference list¶

T9n level¶

• Patch #29045: Change Japanese translation for Tracker
  • https://blog.redmine.jp/articles/japanese-translation-of-the-word-issue/
  • https://lurdan.hatenablog.com/entry/20080224/1204125398
  • Origins of the early translations:
    • source:/trunk/lang/en.yml@278#L97
    • source:/trunk/lang/fr.yml@278#L97
    • source:/trunk/config/locales/fr.yml@21202#L290
• Feature #4178: Optimize Redmine for any project, not just software dev (Change "Version" > "Milestone")
• Feature #2082: Rename Issue as Ticket (or ...) in GUI

I18n level¶

• Feature #34494: Rename the save, edit and delete buttons on the query form to clarify the scope
  • r21191: Rename the save, edit and delete buttons on the query form to clarify the scope (#34494).
• Feature #4908: Change Issue for Task / Feature #4568: Replace "Issue" for "Task"

Conceptual level¶

• Feature #29164: Make the terms overwrite from the Redmine administration screen.
  • https://github.com/ishikawa999/redmine_message_customize
• Feature #17907: Give 'version' another meaning
• Feature #724: change "versions" to "milestones"
• Versions vs Milestones
• Feature #3068: Generic task management (not issues)
• Feature #4636: System-wide Object Label Settings and the general Open Pario Malaise
  • https://github.com/edavis10/redmine_language_change