Project Database, PDB, Onboarding Manual

Our Project Database (PDB) simplifies and streamlines support and development projects for both you and our team. You can effortlessly create cases, whether they involve support, error reporting, or customisation requests. Once created, the information is organized and scheduled within one of our sprints, and then assigned to a dedicated individual or team. We recognize the immense value of collaborating within a common and transparent system.

The PDB offers several advantages, including easy case tracking and complete traceability. It provides a clear record of who performed specific actions, when they did so, and allows you to assign tasks to the appropriate team members while keeping stakeholders informed. Furthermore, it grants all involved parties a comprehensive overview of ongoing projects, their current status, and estimated completion dates.

This is a manual for using our system project database (PDB) →

Need help? Don't hesitate to reach out to your Netset Business Developer or Netset Support for assistance.

Follow the simple steps for a smooth onboarding to our PDB

> Log-in < Once you have received your login information, visit and reset your password (which allows you to choose your own secure password).
> Navigate <In the left menu, you will find search boxes and the menu. To the right of the menu, you will see your project. If you click in there you will enter the project and can see all the tasks added to the project. It is also here that you add new tasks and see the status of these.
> Create or follow up a task < When you create a task, it will end up with the status “New”, and then Netset will reset the status depending on how the task will be handled. When a task is created you have the opportunity to click on a task and get a more detailed view of just that specific task. We would like to see that all communications are kept in the tight task, and this will ensure that everyone involved is updated with the correct information in the process.
> Communications < When communicating through the project database in the task it’s important to choose the right person to communicate with. In the field "Comments" where you write your comment. "Send e-mail to" is where you choose who you require answers from and then who should have mail/notification that there has been an update to the task.
> Follow - up < When a task has been handled by Netset and has, for example, Status Posted on Production, you have the opportunity to first and foremost test so that everything works according to your wishes and then go into the task it is about and changes the status to Approved on production when you feel satisfied if you have any comments or feedback please use the comment field and change the status that fits and follow the communications tips to the left.
> The status changes you make as a customer <

From Time Estimated> Approved for Development
From Ready for Test> Approved on Test
From Operated / Handled> Approved by Customer
Closed without action = The task closes without a specific reason.
Internal customer = The task is paused and the ownership lies with the customer.
Returning to Netset = For some reason, a task is not accepted and returns ownership of Netset.

Last updated 10 months ago

Follow the simple steps for a smooth onboarding to our PDB

> Log-in < Once you have received your login information, visit and reset your password (which allows you to choose your own secure password).

> Navigate <In the left menu, you will find search boxes and the menu. To the right of the menu, you will see your project. If you click in there you will enter the project and can see all the tasks added to the project. It is also here that you add new tasks and see the status of these.

> Create or follow up a task < When you create a task, it will end up with the status “New”, and then Netset will reset the status depending on how the task will be handled. When a task is created you have the opportunity to click on a task and get a more detailed view of just that specific task. We would like to see that all communications are kept in the tight task, and this will ensure that everyone involved is updated with the correct information in the process.

> Communications < When communicating through the project database in the task it’s important to choose the right person to communicate with. In the field "Comments" where you write your comment. "Send e-mail to" is where you choose who you require answers from and then who should have mail/notification that there has been an update to the task.

> Follow - up < When a task has been handled by Netset and has, for example, Status Posted on Production, you have the opportunity to first and foremost test so that everything works according to your wishes and then go into the task it is about and changes the status to Approved on production when you feel satisfied if you have any comments or feedback please use the comment field and change the status that fits and follow the communications tips to the left.

> The status changes you make as a customer <

From Time Estimated> Approved for Development

From Ready for Test> Approved on Test

From Operated / Handled> Approved by Customer

Closed without action = The task closes without a specific reason.

Internal customer = The task is paused and the ownership lies with the customer.

Returning to Netset = For some reason, a task is not accepted and returns ownership of Netset.