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

 Customize your issue fields in the Issue Field Configuration Export knowledge base Export     SubscribeSubscribe      Show article info

The Issue Fields Configuration is available in the 'General'  -> 'Settings -> Issue Configuration -> Issue Fields' menu.

 

You can have as many different Issue Field Configuration as you like and then you choose which configuration you want to use for a project.

 

You can choose to

  • add a new configuration
  • copy a current configuration to use as template when creating a new template (the most right icon)
  • edit an existing configuration

 

Here is a video of how you can use the issue field configuration

 

 

 

This video shows how to create custom fields and then to create an Issue Field Configuration to use the fields. A project is configured to use the Issue Field Configuration and we will see how the fields look when creating a new issue.

 


 

Knowledge Base Images/Icons/star_yellow.gif The general Issue field configurations page:

 

Knowledge Base Images/Settings/Issue Field Configurations.png

 

This page contains a list of issue field configurations.

When a new VisionFlow account is created, there will be one issue field configuration created by default,  named "Default".

 

(Note: It is best to not change the default configuration, but instead copy it and edit the copy instead)

 

Most columns in the table are self-explanatory. The Default column shows which is the default configuration. The action column have two options:

  • Delete - this deletes the configuration. Only configurations that are not used in a project can be deleted.
  • Copy - this creates a copy of the configuration that you can save with a new name and description.

 

Tip: Use the Description field - it helps if you can read what types of projects the configuration is for.


 

 

Knowledge Base Images/Icons/star_yellow.gif The individual issue field configuration:

This page contains several sections. A short summary before the details below:

  • General info : Name and Description of the issue field configuration.
  • Issue fields : These are the issue fields that is used in the configuration, and their settings
  • Fields not included in configuration : These fields exist in the account, but are not used for this specific configuration.
  • Optional "grouping" of issue fields  : Here you can organise issue fields in groups that will be separated with separator lines in the issue page

 

 

Issue fields are generally of two categories:

  • The standard ones that are created along with the VisionFlow account
  • Custom fields - you have to first create these in General > Settings > Issue configuration > Custom fields 

 

 

Issue fields table:

 

This table have a row for each issue field used in the configuration. 

 

The columns in the table are: 

  • Use - This is checked for fields in use. Uncheck this and save to remove the field from the configuration. Note that some core fields are always in use, and cannot be removed (Issue key, Title, Status, Type, Description,  Created, Modified, In progress, Completed)
  • Field name - The name of the issue field. You can find the default name of the field by using the Info icon.
  • Mandatory - checking this makes the issue field mandatory, and it must be set before saving an issue in a project with this issue field configuration.
  • Display - this has two options that controls what issue fields are displayed in a couple of specific cases. For the Issues page, the display is normally controlled by the column view configuration.
    • Issues tab - the fields checked in this column should be the ones shown in the default column view, for example when a new project is created with this issue field configuration.
    • Searches - the fields checked here should be the ones shown in the default search result page.
  • Info - this column contains an icon that you can click on to show a small dialog with more information about the issue field. (Note the color of the icon: Green - Standard issue field, Blue -  Custom issue field.)  The information available in the info dialog are:
    • Name - The current name of the issue field
    • Default English name - The default name of this issue field in English. (This is the name that is used in this knowledge base.)  This is blank for Custom Issue fields.
    • Custom field? - This is "Yes" if the issue field is a custom field, and "No" for standard fields.
    • Custom field name - (Only shown for custom fields) This is the name of the custom field as set in "General > Settings > Issue configuration > Custom fields". You can use different names for the same custom field in different configurations, but here you see the standard name.
    • Field type - (Only shown for custom fields) This shows what type of custom field this is (text field, Single select list, Date field, User field, etc. As of this writing, there are 13 different types of custom fields) 
    • Index  - (Only shown for custom fields) This index is used in some technical cases
  • Field order - this is an order number that controls the ordering of the issue fields. Lower number is placed before higher numbers. Tip: use steps of 10, it makes it easier to insert a new field later, without having to change the numbering of all fields after the new field. 
  • Issue types - this column has a checklist of which issue types should use the issue field. If a type is unchecked, then the issue field will not be available in that issue type at all, for the projects that use this configuration.
  • Access - Click on "edit access"/"hide access" to expand/collapse the access section (Note: Some issue fields are always available, and cannot have their access edited). In this section, you can control the access of the issue field for all the user groups. This is a table with one column for User group name, and two additional columns:
    • Create issue - this column controls which user groups can see or set the issue field when creating a new issue. The options for each group are:
      • Read/Write - Users with this user group on the project are allowed to see and edit the issue field.
      • Read - Users with this user group on the project are only allowed to see the issue field, not edit it. 
      • Read/Write if owner or reporter - Users with this user group on the project are allowed to see and edit the issue field - IF they are set as Owner or Reporter on the issue in question. Otherwise, they are only able to see the issue field, not edit it.
      • No access - Users with this user group on the project are not allowed to see the issue field at all, much less edit it.
    • Edit issue/Issues tab - this column controls which user groups can see or edit the issue field in the "Edit issue" page, in the Issues page, In issue tables and when using context menus. The access options are:
      • Read/Write - Users with this user group on the project are allowed to see and edit the issue field.
      • Read - Users with this user group on the project are only allowed to see the issue field, not edit it. 
      • Read/Write if owner or reporter - Users with this user group on the project are allowed to see and edit the issue field - IF they are set as Owner or Reporter on the issue in question. Otherwise, they are only able to see the issue field, not edit it.
      • No access - Users with this user group on the project are not allowed to see the issue field at all, much less edit it.

 

 

 

 

 

This means that when setting up an Issue Field Configuration, you can:

  • choose which fields you want to use
  • specify the name of the field
  • choose which Issue types the fields should be used for (if they should be used when reporting Bugs, Support Issues, etc)
  • configure the access for the fields for different roles (read, read/write, read/write if reporter or owner, no access)
  • optionally "grouping" of issue fields. You can group related fields and separate the groups with a "separator line"

 

With help of the access for the fields you can for example choose to have a field as 'No access' (=hidden) on the "New issue"-page and have the same field as 'Read/Write' on the "Edit-issue"-page.

Knowledge Base Images/Settings/Edit_Issue_Field_Configuration.png
 


User comments
 Loading ...