Configuring project tools

Configuring project tools

As the Project owner, you can select and configure the project tools that are appropriate for your project. The configuration settings available to you depend on site defaults that are set by an administrator.

Any explicit setting by any project permanently overrides any inherited value. For example, if integration between Project Tracker and version control is turned on by default, you may create a project that makes use of this feature. However, if you do not configure the default behavior from the Tool Configuration page, a site administrator can disable the integration feature and it will cease to work for your project.

To override site-wide default settings for a project:

  1. Log in to the CollabNet platform.
  2. Select a project link.
  3. From the project home page, click Edit project.
  4. Under the Other Operations heading, click Tool Configuration.
  5. Optionally, make changes to the settings.
  6. Click Save Settings .

Project Navigation

The Project Navigation section controls the vertical navigation bars at the left of the screen. Under the section Project Navigation, in Tool Configuration, you have three options. You can turn on or off the Project Tool links, Top Navigation menu or the Project page links:

Note: To learn about replacing the tools section of the left navigation menu section, refer to the help page http://www.[ProjectName].[DomainName].collab.net/scdocs/RemoteBranding.

Version Control: this section will only appear if Project Tracker is the tracking component for this project.

Project Tracker integration
Selecting this will provide a comment in each artifact associated with a commit in the Version control tool. To associate an artifact with a commit, the artifact number must be added to the commit message. This simplifies tracking changes to the source code through the tracking component.
Artifact must be in an Open state
Selecting this will restrict Project Tracker integration with Subversion to artifacts in the Open state only.
Message must name artifact
Selecting this will force every user to add at least one artifact number to each commit message. Using this in conjunction with the Project Tracker integration option will allow you to easily identify code changes made in relation to specific artifacts.
Committer must own artifact
This option will verify that each artifact mentioned in a commit message is owned by the user making the commit. Issue owners then become responsible for verifying the validity of a commit before it is added to the version control repository. This option is only applicable when the Project Tracker integration option is selected.

Documents & files

Maximum file upload size
Your domain administrator or host administrator has set the upper size limit of items added to the Documents & files tool.
Offer to lock new documents
Users who reserve documents for editing can lock the files from edits by others.

CUBiT settings

Enable CUBiT integration
Selecting this option enables integration with the CUBiT application for build and test automation, for the project.

Wiki

Enable project wiki
Selecting this option enables the project wiki tool for collaborative content development.

Project Tracker: this option will only appear if Project Tracker is the tracking component for this project.

Enable email
Once activated, email messages will be sent when a change is made to an artifact.
Detailed email
This option will put the full content of any changes made to an artifact in an email. Be aware that sensitive material entered in a Project Tracker artifact will be sent in the email.
Maximum attachment size
This setting allows you to configure the maximum file size (in MB) for attachments to Project Tracker artifacts. The default value is 150MB. .

Discussions

Maximum attachment size
You can define the maximum attachment size that can be uploaded to a project's Discussions component.
Send posting subjects
Indicates whether or not the discussion posting subject can be used in the subject line of notification emails.
  • Force all discussions to send the posting with the subject.
  • Force all discussions not to send the posting with the subject.
  • Decide at the project level.
Content in email
Determines the option for sending the complete content of a posted message.
  • Send the full content in all emails.
  • Send the content as a link.
  • Use discussion level settings.
Web Posting
Determines the project-wide minimal security level for web posting.
  • Nobody
  • Registered users with the "Message Post" permission only
  • Registered users only
  • Everybody
Email Subscription
Determines the project-wide minimal security level for email subscription.
  • Nobody
  • Registered users with the "Discussion View" permission only
  • Registered users only
  • Everybody
Email Posting
Determines the project-wide minimal security level for email posting.
  • Nobody
  • Registered users with the "Message Post" permission only
  • Registered users only
  • Known addresses only
  • Everybody
Introduce zero-width space
Selecting this option introduces zero-width space in-between long strings to avoid horizontal scrolling.
Reply behavior
In discussion email notifications, you can indicate the default reply behavior for new discussions.
Reject MIME types
Rejects messages having attachments with these MIME Types. Enter one MIME type per line.
Drop MIME types
Drops attachments with these MIME Types from messages. Enter one MIME type per line.
Remove headers
Removes the specified headers from incoming emails. Enter one header per line.
Add headers
Adds the specified headers to the message prior to archiving. Enter one header per line. The format for these filters is name:value.
Reject headers
Rejects the specified headers. Enter headers to be rejected or moderated (if discussion is moderated). Use regular expressions, one per line. Each regular expression must match an entire header. You can use dotall mode and wildcards.
Reject content
Rejects the specified content. Enter message content in discussion body and subject to be rejected or moderated (if discussion is moderated). Use regular expressions, one per line. Each regular expression must match an entire entry. You can use dotall mode and wildcards.

ETL

Enable data harvesting
Selecting this option will enable the "Extract Transform Load" (ETL) mechanism to harvest data for the Tracker metrics tool. Note that when you disable this setting for your project, you will not be able to generate Tracker metrics reports.