Multilingual Support: General Setup: Customizations

Registered by Brian LaVallee

While Eventum is capable of supporting localization, I have noticed some limitations when using the system in a multilingual environment. Specifically along the lines of Statuses, Releases, Categories, and Priorities. When setting up the system, these customizations have to be specified in only one language.

My suggestion would be to use a single table [lang, original, translation] to check against and use the alternative is the users language is not default. Maybe not the most elegant method, but that is my suggestion.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.