CustomNomenclature issues overview » History » Revision 2
Revision 1 (Mischa The Evil, 2021-08-30 07:18) → Revision 2/3 (Mischa The Evil, 2021-08-30 07:30)
h1. Custom Nomenclature issues overview
|{background-color:#FFEBC1; color:#A6750C; padding: 4px 4px 4px 4px; border: 2px solid #FDBF3B;}. *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.|
----
{{>toc}}
h2. 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.
h2. Summary
|_. Current |_. Some alternatives |
| <code>tracker</code> | <code>type, kind, variety, class, category, classification, group, set, genre, genus, species, family, order, breed, race, strain, etc.</code> |
| <code>issue</code> | <code>task, ticket, work item, work package, case, order, request, demand, item, etc.</code> |
| <code>version</code> | <code>milestone, target, phase, stage, iteration, sprint, collection, deliverable, etc.</code> |
| <code>[parent|sub] task</code> | <code>[parent|sub] issue, ticket, work item, work package, case, order, request, demand, item, etc.</code> |
| <code>[issue] subject</code> | <code>[issue] title</code> |
| <code>private</code> | <code>restricted, confidential, embargo</code> |
| <code>status</code> | <code>phase, stage, period, chapter, episode, part, step, etc.</code> |
| <code>% done</code> | <code>progress, progression</code> |
| <code>roadmap</code> | <code>planning, schedule</code> |
| <code>project</code> | <code>department, unit</code> |
| <code>watch[er]</code> | <code>follow[er]</code> |
| <code>news</code> | <code>blog</code> |
| <code>activity</code> | <code>activity</code> |
h2. Forms
|_.Forms |_.Example 'issue' |_.Example 'version' |
|<code>singular-lowercase</code> | <code>issue</code> | <code>version</code> |
|<code>plural-lowercase</code> | <code>issues</code> | <code>versions</code> |
|<code>singular-capitalized</code> | <code>Issue</code> | <code>Version</code> |
|<code>plural-capitalized</code> | <code>Issues</code> | <code>Versions</code> |
|<code>singular-with-indefinite-article-lowercase</code> | <code>an issue</code> | <code>a version</code> |
|<code>plural-with-indefinite-article-lowercase</code> | <code>-</code> | <code>-</code> |
|<code>singular-with-indefinite-article-capitalized</code> | <code>An issue</code> | <code>A version</code> |
|<code>plural-with-indefinite-article-not-capitalized</code> | <code>-</code> | <code>-</code> |
h2. Issue and reference list
h3. 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"
h3. 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
h3. 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"
* message#214
* 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