Downloads (PDF, HTML & XML formats)
[Crucible Knowledge Base]
Documentation for Crucible 3.0.x. Documentation for other versions is available too.
A Crucible project provides a way to group and manage related reviews – typically reviews that are all involved with the same software project. A Crucible project allows you to Every Crucible review belongs to a project. Each project has a name (e.g. ACME Development) and a key (e.g. ACME). The project key becomes the first part of that project's review keys, e.g. ACME-101, ACME-102, etc: By default, Crucible contains one project. This default project has the key 'CR' and the name 'Default Project'.
To create a new project:
Identification |
|
Content |
|
Permission Scheme | Permission Scheme – the permission scheme applied to this project. (A permission scheme controls who can perform particular actions, for example, create a review.) |
Moderator |
|
Default Reviewers |
|
Allowed Review Participants | Use Users and Groups to restrict who can have a role (author/creator/moderator/reviewer) in this project's reviews. These users will be the only ones whose names appear when a review is assigned. Leave these fields blank to allow all users to have access. |
Review Duration | Default duration – the default length of time (in week days) for reviews in this project. If you leave the field blank, then no time restriction is applied. Reviews that are overdue will show up in red on the reviewer's dashboards. Note that the review duration only affects the default due date that appears when creating a review. The review's creator or moderator can specify a different date if they wish. |
Default Review Objectives | Default Objectives – specify some text that will appear by default in the Review Objectives field of each new review. This text can be edited, as with any text in the Review Objectives text box. See Setting default review objectives. |
Screenshot: The Edit Project Screen