Project Default Options

Using Project Default options

Options in this section affect the defaults for all new projects and existing projects that have not ratified or changed the global administrative defaults. When you create a project, the site project default options are inherited by the project. These default settings can be overridden at the project level. For instructions on overriding project defaults, see Configuring project tools.

Framework

• Project language: this feature will only appear if localization is active for this domain.You can select a default language for email generated by events in your project. For more information see About the default project language.
• Preserve HTML head content: Checking this box preserves the head content of HTML files used to customize project content. If projects on your site tend to use Cascading Style Sheets or Javascript in customized project content, it is recommended that you enable this option; however, it is not recommended if users will use office productivity or "WYSIWYG" Web editors to edit this content.
• Project navigation: Determine which navigation options are available to project users.
  • Project tool links: When this option is checked, project pages show a navigation bar at left with links to the tools that are configured for that project.

  Note: Project owners can also turn links to their internal project pages on or off. This capability is enabled by default.

CUBiT settings

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

Data harvesting

• Enable data harvesting: The Project Metrics tool uses the “Extract Transform Load” (ETL) mechanism to extract data daily from the production system, and transform and load it into a reporting warehouse. Reports are generated based on the warehouse data. Check this option to enable the ETL mechanism to harvest data for the Project metrics tool. Note that if you disable this setting for your project, you will not be able to generate Tracker or Subversion metrics reports.
• Subversion reporting data harvesting paths: The Subversion folder paths that are to be tracked for reporting can be entered here. This has the advantage of allowing you to be selective about the directories you want the data harvesting mechanism to run on.
• Excluded Subversion folder paths: The Subversion folder paths that you would like excluded from data harvesting can be entered here. This has the advantage of keeping some directories permanently excluded from being data harvested.

Discussions

• Maximum attachment size: You can define the maximum attachment size that can be uploaded to a project's Discussions component.
• Send posting subjects: You can specify whether to use the discussion posting subject in the subject line of notification emails or not.
• Content in email: Using this option, you can specify the inclusion of contents of a posted message.
• Web Posting: This setting enforces the domain-wide minimal security level for web posting.
• Email Subscription: This setting enforces the domain-wide minimal security level for email subscription.
• Email Posting: This setting enforces the domain-wide minimal security level for email posting.
• Introduce zero-width space: You can introduce a zero-width space in-between long strings to avoid horizontal scrolling, by selecting this option.
• Reply behavior: In discussion email notifications, you can indicate the default reply behavior for new discussions.
• Reject MIME types: Using this option, you can reject messages having attachments with the specified MIME Types.
• Drop MIME types: Using this option, you can drop attachments with the specified MIME Types from messages.
• Remove headers: You can set the option for removing the specified headers from incoming emails.
• Add headers: You can set the option for adding the specified headers to the message prior to archiving.
• Reject headers: You can set the option for rejecting the specified headers.
• Reject content: Setting this option rejects the specified content.

Documents & files

• Maximum file upload size: You can define the maximum file size that can be uploaded to a project's Documents and files component.
• Offer to lock files: You can enable or disable the ability for user to lock files when they are first created in a project's Documents and files component.

Wiki

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

Project Dashboard

• Task reporting period: The task reporting period can be set as Weekly, Fortnightly or any another period in number of weeks.
• Plan Synchronization: The plan file will automatically get synchronized with the tasks completed, at a particular time of day depending on the time and frequency set.
• Task Discussions: Existing default lists can be used. For example cvs, commits, issues, admin. Alternatively you can create a new list named "planning" whose properties can be edited.
• Personal tasks: Once activated, will enable you to create personal tasks with project planning.
• Project Status Rule: This option will help you select which tracking measurement should be used to determine the status of the project. For more information on tracking measurement refer the documentation in "About Project Dashboard."

Project Tracker

• 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.

Related Artifact Notification

• Parent: When an artifact is modified, the users associated with related artifacts will be notified. On selecting this option, the parent artifact in a relationship to an edited artifact will be notified.
• Children: On selecting this option, the child artifacts of the edited artifact will be notified.
• Blocker: On selecting this option, the artifacts that are blocking the edited artifact will be notified.
• Blocked: On selecting this option, the artifacts that are blocked by the edited artifact will be notified.
• Otherwise related: On selecting this option, the artifacts in the otherwise related category will be notified.
• Duplicate (dominant artifact): On selecting this option, the dominant artifact of the edited duplicate artifact will be notified.
• Duplicate: On selecting this option, the users associated with duplicate artifact will be notified.

Version Control: CVS and Subversion

• Project Tracker integration: This option only affects projects with Project Tracker as the tracking component. 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 ID must be added to the commit message. This simplifies tracking changes to the source code through the Project Tracker component.
• Message must name issue: Selecting this will force every user to add at least one artifact id 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. Artifact 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 Tracker integration option is selected.

Top | Help index