User information
 Loading ...
Show article in Knowledge Base

 Creating a new project Export knowledge base Export     SubscribeSubscribe      Show article info

How to create a new project:

You can create a project in a few different ways in VisionProject.

The most common way is to create it from the Projects panel on the left, by choosing 'New Project'. Another common way is to choose 'Create Project' from the Quick Links panel on your Dashboard.




The "New project" page opens in a new tab, and contains several options for you to choose - many of which are checked by default.

The "New project" page is divided into 2 parts. The top part is specific information about what kind of project this is, including what the Issue key prefix should be.


If you want a quick project using default settings, just enter name,  description and issue prefix (such as DEV, TEST, WEB), then Click  "Create".



General information:

  • Project Category - You  might want your project to be grouped in different categories. This is  the place for it. If the category you want is not available, click  "Manage" to create a new category. Find more information about categories here.
  • Company (owner) -If you have  a customer company that should 'own' the project, choose it from the  list of customer companies that you have defined on your account. If it  is not available, then create the project, and assign the owner later,  after you've created it in the Companies tab.
  • Name - The name of the project. Tip: use as descriptive a name as possible, to avoid confusion as to what the project is about.
  • Description - Here you can enter a longer description of the project.
  • Start date - If the project has a defined start date, you can enter it here.
  • End date - If the project has a defined end date, you can enter it here.
  • Project budget - If you have defined a budget for the project, enter it here.
  • Use  sprints - Uncheck this box if you do not use sprints in the project.  This hides the sprints page, and affects how resource availability is  done. With sprints, you can set work hours on them - and if you do not  use sprints, work hours are set at the project level only.


Issue Key prefix:

  • Defines  what prefix the issue tracking is using for this project. For example,  if you enter SHOP, all issues will be numbered SHOP-1, SHOP-2, etc. It is highly recommended to use an issue prefix to be able to associate the issue to a project when for example discussing the issue with colleagues.


The second part enables you to have decide to use the default settings around Priorities, Notifications, Workflow, Issue Types and Issue Statuses. If you don't want to use the standard settings, you can change that here.




  • Select the checkbox to use the default project priorities (Very Low, Low, Medium, High, Very High) instead of number type priorities (1,2,...,n). The names of priorities can easily be changed afterwards in the account settings.

Notification and Workflow:

  • Select the checkboxes if you want to create a default set of notifications and workflows, that you then can adjust in the Project Settings tab Notifications and Workflow, respectively.

Issue types:

  • a list of issue types to be used in the project. Just check those you want to use. The names of issue types can be changed by the administrator, so your account might use different names for the issue types.

Issue statuses:

  • a list of issue statuses to be used in the project. Just check those you want to use. The names of issue statuses can be changed by the administrator, so your account might use different names for the issue statuses.

When you have made your choices, click "create". The content of the tab will show two links:

Go to the project - Clicking on this will open the newly created project in its own tab, and focus on it.

Create a new project  - this will create a new project form in the tab, for your next new project.


The user that creates the project will be added as a project member with the role 'Project administrator'.

Note: that a user can have different user roles in different projects.


A user can also be set to only see "Assigned issues". This means that the user will only have access to issues where she is the Reporter, Owner or Developer. (This is done in the project page -> Users subtab -> Manage users for this project.)

User comments
 Loading ...