User information
 Loading ...
Show article in Knowledge Base

 The Project Settings page ‑ General Export knowledge base Export     SubscribeSubscribe      Show article info

This is where you manage settings specific to the given project.


Note: Other settings are on a company level (affects all projects in the company), and can be accessed by selecting Settings in the General panel in the left navigation sidebar.


The Project settings have several sub-tabs:


Knowledge Base Images/Project Settings/Project_Settings_Subtabs.png


  • General - Basic settings for the project, mostly related to issues. This is the default sub-tab.
  • Notifications - Which events should trigger email notifications, and who should be notified. Read more about notifications here.
  • Workflow - Transfering ownership of issues on status change. Also which status changes should be allowed. Read more about workflow here.
  • SLA escalations - Actions and notifications triggered by time related criteria, for example when an issue has been unchanged for a specified time. Read more about SLA escalations here.
  • Email - Settings for the email ticketing functions for creating issues of incoming mails, and other support related functions. Read more about the email ticket system here.
  • Cost - Different models of configuring cost/billing rates, if you use this in the project. Read more about configuring costs here.
  • Simple forms - Information on how to have input forms outside of VisionProject to create issues in VisionProject. Read more about simple forms here.
  • Issue templates - Shows all issue templates on the project. A template issue have some fields already pre-filled when creating it. Read more about issue templates here.


This article focuses on the General sub-tab. There are several sections, which can be expanded/collapsed as you like:




 Edit Project Info : This section contains important information about the project itself


Note: This section was earlier its own page, but it has now been consolidated into Project settings -General. 


Knowledge Base Images/Project Management/Projects_Edit_Info_smaller.png


General information:

  • Project category - Projects can be grouped in categories, which besides being descriptive helps navigating the projects panel to the left. Select a category in the dropdown list. If no category is suitable, click on 'Manage' to open the project category editing page, to create a new category or edit an existing one. You can find more information about managing categories here.
  • Company (Owner)  - Which company owns the project.
  • Name - The name of the project.
  • Description - In short, what the project is about
  • Project lead - Which user has the project lead role.
  • Start date - Project start date.
  • End date - Project end date.
  • Project budget - The budget of the project. Currently only a text field.
  • Status - Active or inactive. Inactive projects are not shown in the project list. Note: You cannot delete an active project, you have to set it as inactive first! Inactive projects are visible in the project panel actions -' show inactive projects'. Find more information about how to delete a project here.
  • Product - the Product/Asset/Config item associated with the project.
  • Use sprints - If the project uses sprints at all. Note: What we call sprint is known by many other names - iteration, sprint, milestone, etc.



Project custom fields: 
This section is only shown if you have any custom fields on the project. The fields are grouped on sections. You can configure project custom fields and their grouping in the account settings (General - Settings - Other settings - Custom fields - project)


Issue key prefix: 
The string entered here will be used as a prefix for the issue keys in this project. If you use, say 'ABC', then all project issues will be named [ABC-1], [ABC-2], etc.. Use something that is specific to the project, and short if possible. It is highly recommended to have a prefix to easily know what project the issues belong to.



Check this if you want to use the predefined priorities (Very Low, Low, Medium, High, Very High), instead of the numbers (1,2,3,4 and 5).


Copy button: Clicking this will make a copy of the current project. You can find more information about copying a project here.





[Start optional section]


Custom fields : This section contains up to five project custom issue fields. Note: This is a legacy section from when custom fields were only on project. This function is not used for customers who starts using VisionProject after 2009. We recommend that you instead create custom fields on account level, and add them to the issue field configuration the project uses. This has advantages as you cannot search on the project custom fields, for example.

Every custom field has some attributes needed

  • Name - Enter the name of the custom field
  • Mandatory - Check this if you must set the custom field when creating an issue
  • Display in issues tab - Check this if the custom field should be visible in the Issues page
  • Visible for support users - Check this if support users should see this custom field or not.
  • Field type - What kind of data the custom field has. Select one of several options possible:                
    • Text field - enter any text
    • Select list - single select from a dropdown list
    • Yes/No - just two possible values, yes or no.
    • Date field - enter a date.
    • Multi select list - select several options from a dropdown list.
    • User (no support users) - a user in VisionProject on the project. Does not include support users.
    • User(with support users)- a user in VisionProject on the project. Include support users - i.e. all users.
    • Date + time field - a date and a time.

Edit your custom fields and press the Update button to save.



[End optional section]



Issue types : This table shows a list of issue types defined on the account. Select the issue types to use in this project by checking the checkboxes under the column 'Use'. Issue types can be created/edited/removed in the general settings (General - Settings - Issue configuration - Issue types).


Knowledge Base Images/Project Settings/Project_Settings_Issue_Types.png


The columns are:

  • Use - If the issue type is used in this project or not. Checkbox.
  • Name - The name of the issue type.
  • Description - A description of the issue type, perhaps what it is used for.
  • Icon - If you have an icon for the issue type, it will be shown.
  • Default - Which issue type is the default. It is possible that two types both have the default flag, then the first one is used in this project.
  • Order - The internal order among the issue types.
  • Group access - What User Groups who have the rights to create an issue of the specified issue type.

To change the issue types used or the rights, just click/unclick the relevant checkboxes, and press the Save button.




Components : This section shows an editable table of components used in the project. Components can be used to group issues, or just as a way to identify what the issue concerns. You can easily edit your project components in the table, just selecting a row, edit name / description, and click on Save.


Note: We recommend using Product/Services/Configuration Items instead of Components, as Components are limited to a single project, while Configuration items are on account level and available everywhere. This helps when copying/transfering issues between projects, for example - the Config Item can be retained.


Knowledge Base Images/Project Settings/Project_Settings_Components.png


The columns are:

  • Name - The component name. Editable textfield.
  • Description - More info about the component. Editable textfield.
  • Action - what to do with the component. Currently the only option possible is the 'delete' action. Just click on it to delete the component.


Add new component - The section below the component table is for creating more components. Add a name and description and click on the 'add' button to add the new component.




Project tabs : In this section you can set in what order the project tabs should be shown in and who should have the rights to what tabs.


Knowledge Base Images/Project Settings/Project_Settings_Project_tabs.png


The columns are:

  • Tab name - This editable textfield contain the name of the tab. Just rename it to something that suits your project better.
  • Tab order - This editable field contains the order number of the tab. Lower number comes to the left of higher numbers. (1 is the leftmost tab)
  • Access - This section has a column for each user role, with a checkbox for each cell. For each user role, just check/uncheck which project tabs the role should see. Note: the settings tab is always available for administrator and project administrator roles.

Edit the tab settings, and click Save to save.




Issue field configuration : This is a dropdown list of available issue field configurations you can choose for the project. Just select one and click Update, to set the configuration. Issue Field Configurations (IFC's) determines which issue fields (including custom fields) are used/displayed, for which issue types and what the accesses are for user groups. Note that you can only create/edit IFC's in the general settings. (General - Settings - Issue configuration - Issue fields)


Knowledge Base Images/Project Settings/Project_Settings_IFC.png



Choose the issue field configuration, and click Save to save.




Statuses : A table of which statuses the project uses, for which issue types, and the accesses for different user groups.


Knowledge Base Images/Project Settings/Project_Settings_Status.png


The columns are:

  • Use - If the status is used in the project or not. Checkbox.
  • Name - the name of the status
  • Issue types - this section has a column for each issue type. The selected check boxes are reflecting what statuses are used for what issue types.
  • Group access - this section is expandable, just click on the Edit access to expand the sub-table for the status row ( the sub-table can easily be collapsed by clicking on the 'Hide access') :                
    • User group - Every user group has its own row in this column.
    • Access - A dropdown list for each user group, with the following options:                
      • No limitations - the user group can do anything with an issue having this status
      • Unable to change the status - The user group can do everything except further changing the issue status for an issue with the status in question.
      • The issue is read-only - The user group can only read issues having this status.


Edit the status settings, and click Save to save.




Sub-issues : How sub-issues are used in the project, if at all.


Knowledge Base Images/Project Settings/Project_Settings_Subissues.PNG


The checkboxes are:

  • Enable sub-issues for this project : Check this to use sub-issues. This is needed to use any of the other checkboxes at all.
  • Hide sub-issues on the first level : Check this to only show sub-issues under their parent issues (if parent-issue is shown on the same page in the issue list). If this is unchecked, sub-issues will be visible both under their parent issue and on their own in the main issue list.
  • Aggregate time from sub-issues on parents : This will make time values on parents the total of the values for the children, plus the values for the parent itself. This has three subordinate checkboxes for the different types of times that can be aggregated. Just check the ones you are interested in (or all):                
    • Estimated time - The time you think the issues will take.
    • Actual time - The time that has been actually spent on the issues
    • Remaining time - The time left to work on an issue.
  • Let parent inherit start date and due date from sub-issues : Check this and the parent start date will be same as the earliest start date of the children. The due date of the parent will be the latest due date of the children.
  • Close parent when all sub-issues are closed: Check this to automatically close the parent issue when all its subissues are closed.
  • Set parent status to X when sub-issue is in progress: Check this to automatically set the parent status to the defined status (Default is Work in progress) when one of its sub-issues is set to "In progress". This is typically used when you have set up work to be done as parent + sub-issues, so that the parent is in-progress when work has started on one sub-issue. The statuses available to choose are the ones with the In-progress flag.
  • Close sub-issues when parent is closed: Check this to automatically close all open subissues when the parent is closed.


Edit the sub-issue settings, and click Save to save. 




 Version control integration : If you want to use a version control system on the project. This can be used to tie code submits to an issue in VisionProject. Currently, we only support one version control system, Subversion.


Knowledge Base Images/Project Settings/Project_Settings_Version_Control_Light.png


There is only one checkbox:

  • Enable VCS integration (svn) - Check this to enable subversion integration. This will open up more fields for configuration. Read more about this here.


Edit the VCS settings, and click Save to save. 




Documents : You can here choose to use version control on documents. This is useful to see when project documents have been changed/updated. In some cases (text/html), you can even compare versions to view what changes has been made between versions. (These functions are in Edit document in the Documents tab)


Knowledge Base Images/Project Settings/Project_Settings_Documents.png


There is only one checkbox:

  • Activate version control on documents  - check this to use versioning on the project documents.


Edit the Documents settings, and click Save to save. 





 General issue settings : This is where you can activate the possibility to Quick Add issues in the issue list. This enables you to add issues directly in the list, and therefore not using the form to enter issues.


Knowledge Base Images/Project Settings/QuickAddIssueSettings.PNG


The checkboxes are:

  • Enable quick issue in issues tab - check this to enable the possibility to enter new issues directly in the issues list. You can customize which issue fields should be available in the QuickAdd feature. Title, Type and Description are always available. The other fields to make available are:              
    • Status
    • Developer (or Assignee/Responsible user/et.c if terminology has been changed)
    • Reporter
    • Current Owner
    • Owner group
    • Est. time
  • "Owner group" and "Owner" fields should be dependent - check this to make these dependent of each other. The fields will behave like this:              
    • When Owner/Current Owner is set, then the Owner group will be automatically set to the user group that the owner belongs to.
    • When Owner Group is set, then the selection in the Owner field combo will be limited to users having the selected user group.
  • "Company" and "Reporter" fields should be dependent - check this to make these dependent of each other. The fields will behave like this:              
    • When Reporter is set, then the Company field will be automatically set to the Company that the owner belongs to.
    • When  Company is set, then the selection in the Reporter field combo will be limited to users belonging to the selected Company.


Edit the settings, and click Save to save. 





 Support Chat : These settings control how the support chat behaves in the project. This section will not be shown unless you have activated the chat module, and the support chat, in the account settings.


Knowledge Base Images/Project Settings/ProjectSettings_SupportChat.PNG


The options here are:

  • Support chat enabled - check this checkbox to enable the support chat for the support centers in the project. You still need to add the support center image/link to the design page, so that support users can initiate support chats.


  • Welcome text(used by support chat) - The text entered in this textarea will automatically be sent to the support user when the chat starts, as an initial "Hello, welcome to the support chat for Company X. What can I help you with?".  


  • XMPP Link:  This link opens a small popup showing the host name and room name for support chat on the project. This allows connection to the project's support chat using a freestanding XMPP client.


Edit the settings, and click Save to save. 






 Issue timer/Work log settings : These settings control the timer functionality on issues, and how work logs should be handled.

Read more about issue timers here.


Knowledge Base Images/Project Settings/Project_Settings_IssueTimers_Worklogs.PNG


The options here are:


  • Automatically create a work log for the time it takes to create a new issue - When this is checked, every time you select "Add new issue", the timer will start running. You can then take your time inputting values in the "new issue" form. When you then press save, and the issue is created, the timer stops running, and the time it took to create the issue will automatically be set in a work log on the issue. The text for that work log is "Issue created".
  • Work log category should be mandatory - if this is checked, you cannot save a work log that does not have the category set. If you try, you'll get a validation message that tells you to set the category.
  • Allow time to be reported directly on the project and not just on issues - If this is checked, you can enter work logs on the project itself in the Project info tab, if you have permission to do so. 
  • Use issue timers - check this to enable issue timers on the project
  • Work log option when stopping issue timers - this controls what should happen when you stop the timer (Either manually or by setting the issue to a status that have the "Stop timer" flag set.)  
    • Never create work log - work logs are never created automatically when the issue timer stops. You can still manually create a worklog for a stopped timer.
    • Create work log and show work log dialog - When stopping the timer, you will be shown a work log dialog where you can enter the worked time, including setting category and write some note if you want to.  
    • Automatically create work log - when stopping the timer, a worklog with no name and blank category will automatically be created without prompting you. 




User comments
 Loading ...