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

 The Terminology page Export knowledge base Export     SubscribeSubscribe      Show article info

The terminology page is where you can change the words used for certain concepts

 

This page is available in account Settings - Other configurations -Terminology.

 

The idea behind terminology configuration is like this: Some key project terms often differs a lot, depending on things like company culture, what project processes/frameworks people use, and simply language. For example, 'sprint' might not feel relevant to you, while 'Iteration' might.  By choosing predefined options and/or editing term values, you can make VisionProject use terminology appropriate to your circumstances.

 

Note: VisionProject terminology currently (v 13.0) only manages terms for these concepts (Using the default names):

 

  • 'Version' / 'Iteration'  (Which is default depends on the age of the account)
  • 'Developer(The issue field)
  • 'Issue
  • 'Products (The catalog/collection/inventory)' - this option is  mostly only used for the label in General - Settings
  • 'Products' - this option is used for most other cases where Products are used in text. 
  • 'Contract'
  • 'Project'

 

More terminology options will be available in later versions. We welcome customer feedback on what words/terms should be available for customization in Terminology, so if you have an idea, feel free to mail us !

 

 

The page contains two sections - select boxes for predefined options, and a table of individual term key-value pairs, both normal and special terms.

 

Knowledge Base Images/General/TerminologyPage_tagged.png

 

Knowledge Base Images/Icons/number_1_blue.gif Predefined options

To choose a predefined option, just select a combobox and choose the result. This will result in the target word being substituted with the new selected term. You might see an update in the resource key table as well.

 

Table of key-value pairs

This table has one column for the internal resource key, and another for the value - the actual word/sentence being shown in VP.

  • Black text in textfields - Default values.
  • Blue text in textfields - Custom values.
  • Rows are grouped in categories, like 'sprint' and 'developer' (The target words for a terminology change).
  • Edit the values by clicking in the text field, write the new word/sentence and remove focus/press enter
  • Clear custom values by clicking on the delete 'X' button next to the row. The term will still exist, just that its value will be set to the default value.

 

Knowledge Base Images/Icons/number_2_blue.gif Special categories. These keys are used for internal substitution, and can be also be updated by choosing a predefined option. Ordinary keys often contain a substitution key referring to a special 'nomen' key. Most basic categories have a corresponding special category. (It really depends on the language, and our internationalisation.) The special categories section may be absent in some languages. If so, you will have to edit the basic terms directly.

 

Note about internal substitution: The substitution keys look like this: @{nomen.abc}@. Everything between the @-signs will be substituted with the special key inside the parentheses - in the example 'nomen.abc'). 

A sentence like this ('This is a test version for demonstration') can be applied to milestones, sprints, iterations etc., by having the substitution 'This is a test @{nomen.version}@ for demonstration'.

 

Knowledge Base Images/Icons/number_3_blue.gif Basic categories. These key values are often entire sentences. Regardless of what option is chosen in the special or predefined key-values, you can enter the text you want in the textfield for the relevant keys. Basic terms are the ones actually overriding the default terms. Special category terms and predefined options give greater flexibility, but in the end, they are about customising the value for the basic term.

 

Where is the text located in VisionProject? We have tried to give the keys descriptive names, to make it easier to know where the key/value is used inside VisionProject. If you have any questions, feel free to mail us.


User comments
 Loading ...