Actions (Project's Dashboard)


The actions section on Project's Dashboard contains two sets of features:

Project Actions
Project Membership Actions

Project Actions

Actions for managing the Project contains:

Milestones, Project's tasks, Hour lock, Price models, Project's roles, Copy project, Merge to another project and Project mapping.

Different action features for a project
Milestones allows you to set milestones for your project. Clicking the icon opens a window, in which you can see previously created milestones and in which you can create new milestones.

Project's tasks allows you to set different tasks for your project. Clicking the icon opens a window, in which you can see previously created tasks and in which you can create new tasks.

For this project we have added two tasks: Documentaition and Writing & General work

When you click 'Add a new task' a new area opens in the modal, which allows you to specify your task a little more:

Add in details about the task

Task name = Define the name for the task
Estimated hours = If you have an estimate of total hours for the task you can specify it here. This will also show in the Timesheet if you have the functionality enabled.
Task type / Invoiceable = whether or not the task's work is considered billable or not. In order for the task to show up in Extensive Project Report this needs to be set as 'Invoiceable'
Task type / Active = whether or not the task is currently active. This also dictates whether or not actual hours can be registered for the project's task.

Tasks are used to specify what kind of work is done in a more detailed level. Actual hours are always registered on task level.

Hour lock opens a new window in which  you can lock hours:
Locking hour registering for a project

Price models opens a window for settings up prices for actuals (actual hours) in different possible scenarios. The first applicable price that is set from the top to bottom will be the one used for pricing, hierarchy being:

Task prices > People Prices > Other prices.
The price model view in Silverbucket

An example scenario:

Person named "Help & Manual User" works 10 hours for the 'General work' -task. The price for this would be picked from the People Prices -slot (10 hours * 20 Euros = 200 Euros), as 'General work' has no price set.

However, if "Help & Manual User" spent 10 hours with the "Documentation and Writing -task", the price would be picked from the Task Prices -slot instead, task prices being higher in the hierarchy. (10 hours * 17 Euros = 170 Euros).

Project's roles -button provides you detailed insight about the allocations by roles or by people.

Detailed information about roles and their allocations for the project

Copy Project -tool is a powerful tool to create multiple similar projects in Silverbucket. The copy project -dialog allows you to choose which attributes to copy and move to a fresh new project.

The Copy Project -tool will always create a brand new project, and name it "Copy of <project's name>" Note: the project, which is used to take the copy from, will remain exactly the same.

You can copy the following attributes from one project to another project:

Tasks, Milestones, Budgets, Project tags, Invoicing details, Prices and Roles. Under 'Roles' you can also copy the users and their reservations according to their roles. And even more, you can move the allocations to start from a specific date. When copying allocations to a new project, the hours will always be shifted starting from the closest full week to address any unwanted situations in the project (for example allocating hours for weekends)
Note: activating the "Roles" slider (similarly the "Reservations" slider afterwards) gives you more options about copying the allocations. See screenshot below.

You can decide which information gets carried over for the new project

Merge to another project adds the current project's allocations, actual hours, budgets, price models, tags, portfolios, milestones and users to the desired destination project. Source project will be permanently deleted.

Project mapping is used only with hour integrations. It maps the actual hours from one project to another project. This feature is not necessary unless Silverbucket support adviced you to use it.
How did we do with this article?