Customers
User information
 Loading ...
Show article in Knowledge Base

 Localising VisionFlow Export knowledge base Export     SubscribeSubscribe      Show article info

 

Localising VisionFlow

 

There are two parts to localising VisionFlow - changing the language setting, and translating the names of many configurable items (Issue types/statuses/priorities, project tabs, for some examples). Even if your language is not present in VisionFlow yet, you can come quite a bit just by translating the names of configurable items. Note that if you are running the installed server version you can translate VisionFlow to any language you like.

Currently, VisionFlow supports several languages beyond English and Swedish. Read here: The list of supported languages.  

In the future we will also support other languages as they are requested. If you have any questions regarding this, feel free to contact us at support@VisionFlow.se.

This article assumes you are logged in as an admin with account rights. It also assumes at least VP version 12.0.  (The names of all tabs can of course differ depending on the users current language settings – this article assumes the user is going from English to a different language.)

 


1. Changing Locale/Language settings (On account level)
 Go to General- Settings- General – General. Go to the Default locale field and choose the target language in the scroll list. Click on the Update button.
This changes the language of ordinary text but not for configurable attributes – several steps remain until VisionFlow looks entirely localised.

 

 

 2. Change issue fields/”headers”
 This is split into two parts, to create a new issue field configuration, and lastly to choose it for a project.

2a) Create a language-specific issue field configuration
 Go to General - Settings - Issue configuration - Issue fields. Add a new issue field configuration, enter a name and description - preferably something with the language name in it, so you know it is for the localisation. The configuration will be added to the list of issue field configurations.

 

Click on the relevant configuration, and you will see a table with all issue fields and their properties. Focus on the column 'Name', edit each issue field name directly in the table, renaming it to something suitable in your language. Save all changes by clicking on Update. 

2b) Choose the language-specific issue field configuration at the project level
 Open a project and go to - Settings tab - General issue setting - Issue field configuration. You should now be able to see your newly created language-specific issue field configuration in the scroll list. Choose it, and click Save.

The headers in the issue list should now be language specific. This setting is project dependent, so if you have several projects, you must repeat step 2b for each project to be localised.

 

 

3. Change statuses, types, severities and priorities. 

These are account specific, so changes here will affect all projects!

Go to General - Settings - Issue configuration. All these items have their own sub-tabs here. 
 

 

  • Issue types: Here, you can easily change the names of the issue types right in the list. Add new types if needed. Remember to click on Save.
  • Issue statuses: This list is organised differently. You have to change each status by clicking on the edit icon in the 'Action' column on the far right. That will show you a pop-up window where you can change the name and description to suitable translated text. Edit all statuses in this way. Add new statuses if needed and when you’re done click on Save.
  •  Issue severities: This list is set up in the same way as for the Issue statuses. Edit each severity by entering name and description in the edit popup. Remember to click on Save.
  • Issue priorities: This list is set up in the same way as for the statuses. Edit each priority by entering name and description in the edit popup. Remember to click on Save.
  • Issue escalation levels: This list is editable immediately. Choose to eiher change the rows and press Save or add a new row by clicking Add new issue new escalation level. Remember to click on Save.
  • Issue resolutions: This list is set up in the same way as Issue escalaton levels. Choose to either change existing rows or Create new resolutions. Remember to click on Save.
  • Interaction statuses: This list is set up in the same way as Issue escalaton levels. Choose to either change existing rows or Create new interaction statuses. Remember to click on Save.
  • Issue source: Specify the default issue source by picking the default value inthe list.Remember to click on Save.
  • Custom fields: This list looks similar to the status one, but the dialog is a little different. Name is edited in the popup as before, but if the type of custom field is a 'select list', you need to edit all the rows in the 'options' box as well. Remember to click on Save.  
  • Action buttons: This list is set up in the same way as for the Issue statuses. Edit each action button by entering name and description in the edit popup or Add new action button. Remember to click on Save.

 



4. Change the names of the project tabs.

Go to the project - Settings - General - Project tabs. Here, you can change the names of the tabs directly in the list. Choose suitable translated names. Remember to Save.


5. Change names of the searches/filters.

In the Searches tab of the navigation panel at the bottom left, is a list of saved searches/filters. To edit these, click on the edit icon, which takes you to the Searches/Filters page for that search, where you can edit it. You can also rename it by pressing Save and changing name and description in the dialoge that opens up.

Note: Some default search filters could be translated already, by choosing language in step 1. These default translations only work if the name of the search/filter matches the default name exactly. For example, if you have changed the name of the search 'All issues' to 'All issues available', this default translation will not work. You will probably have created your own custom filters, and these has to be translated individually.


 After these steps, VisionFlow should be localised for the relevant language. If you see something that looks wrong, feel free to contact us. 


User comments
 Loading ...