This documentation relates to Crucible 2.7.x

If you are using an earlier version, please view the previous versions of the Crucible documentation and select the relevant version.
Skip to end of metadata
Comment: Corrected links that should have been relative instead of absolute.
Go to start of metadata

To browse the content in a project, click the Projects tab at the top of the page. The 'Projects' view opens (see 'The Crucible Projects Index' screenshot below).

A list of projects will be shown if there is more than one. Click the name of the desired project to open it. The 'Project Activity' page opens (see 'The Crucible Project View' screenshot below). In the left navigation bar, charts showing overall project statistics are displayed.

There are a number of sub-tabs on this page, listed in the table below.

Sub-Tab Name

Description

Activity

  • All Activity — The default view.
  • Commits — Shows commits in the project (visible when using FishEye).
  • Reviews — Shows reviews in the project.
  • Issues — Shows JIRA issues related to this project. (info) Only visible if you have set up JIRA integration in Crucible.
  • Show Revisions — Shows or hides revisions in the project (visible when using FishEye).
  • Earlier Activity (Left Arrow icon) — Loads a page of earlier project activity.
  • Later Activity (Right Arrow icon) — Loads a page of later project activity.

Reviews

Shows recent reviews in the project.

(info) The Projects tab is only visible in Crucible. Read more about the definition of a project.

Screenshot: The Crucible Project View

Screenshot: The Crucible Projects Index

Labels:
None
Edit Labels

1 Comment

Hide/Show Comments

  1. Jan 12, 2012

    Ron Summers

    A couple of things.  From the way the top paragraph is written, shouldn't the second screenshot (projects index) be first since you come to that before you go to the specific project?  That is the sequence given in the wording.

    Also, we have an Expand All button, not a Show Revisions.  We are still running 2.5.4 but I looked at the documentation for 2.5 and 2.7 and it is the same.  So either software had an error (in 2.5) and has been fixed (in 2.7) to match the documentation or the documentation is in error and doesn't match the software.