When changing language on the account, you might see some texts that are not translated properly.
Why is this?
1.) It can be a bug in the internationalization files, that we've missed some texts.. This is likely if it is only a few words/sentences here and there. In this case, please inform us of missing texts.
2. The other case is that you are looking at certain fields that are user configurable on account or project (For example issue statuses, types, priorities, the names in the default field configuration, et.c). These are stored in the database instead of a language file. The translation deals with these in a different way.
VisionFlow tries to translate these values, but if the values have been changed from the default settings (i.e. it has a custom name for that language), the system leaves the value alone.
So you can get a mixture of two languages. For example, if you have new issue types/statuses/etc.. or custom names for them, then VisionFlow might only translate the default ones, leaving the custom ones alone - resulting in a language mix.
Note: The translation of these fields generally work when you change the account language once.
If you change language back and forth, it may result in some fields not being translated back to the original language.
You can manually update these things back in the Settings tab for the account settings, and in the settings sub-tab of a project, for its project settings.
The fields that you might need to update yourself are:
- Issue types - names and descriptions
- Issue statuses - names and descriptions
- Issue severities - names and descriptions
- Issue priorities - names and descriptions
- Custom Issue fields - names
- Issue fields in the 'Default' issue field configuration - names
- Roles - names
- User groups - names
- Custom User fields - names
- Components - names and descriptions
- Project tabs - names