Creating a Project
A project defines everything you see in a Web view: the fields, queries, reports, sorts, and layouts.
How Many Projects Do You Need?
Each project has its own issue database.
For example, you can record different types of issue in separate databases by creating separate projects. Separate projects mean smaller databases and better performance. They also mean you can customize the fields, queries, sorts, layouts, and reports, so you can simplify your Web Views.
However, tracking issues in separate projects has some disadvantages:
You
cannot generate reports across all projects.
You
cannot create a single view that covers all projects.
You
cannot link items from different projects
People
who work with all three types of issue can find that separate projects are inefficient and time-consuming.
Choosing a Base Project
A base project serves as a starting point for a new project. The new project inherits the fields defined in the base project, and can optionally inherit the styles (queries, reports, sorts, layouts, and notifications) and Web views as well.
Vector HelpDesk includes a default HelpDesk project you can use as the base project. Before you create a new project based on HelpDesk, you should familiarize yourself with the fields included in HelpDesk, and understand what you can and cannot do when customizing fields.
Designed for use in development projects, HelpDesk allows you to record and track project-related tasks, feature and enhancement requests, user suggestions, and change notices.
HelpDesk includes over 60 fields, along with a complete set of reports, queries, sorts, layouts, and notifications based on those fields. Some of the default fields cannot be deleted, so even if you don’t use these fields, they take up extra space in your database.
Before you delete a field, you must remove it from any report, query, sort, layout, or notification that references it. Deleting unused fields helps minimize the size of your database.