All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Project Settings (Admin)

Project Admin contains setting grouped in sections.

  • General contains admin pages for basic settings and permissions/subversion -- for permissions see HelpAdmin/ProjectAccess.
  • Blog settings -- described below, see HelpUser/Blog for more information.
  • Discussion system settings -- see HelpUser/Forum for further information about this module.
  • Ticket System settings -- further descibed below, and see HelpUser/Tickets for more information.

Basic Settings

The administration page for basic project settings allows:

  • Updating a short Description of the project for use in project listings and similar.
  • Enable or disable Email Notification for sending email notification of ticket changes.
  • Enable or disable Ticket Ownership Restiction that restict ticket ownership (re)assignment to valid users with assigned permissions to the project.
  • Upload and replace Project Logo (in header).
  • Edit New Ticket Text - text to be displayed at the top of the form for submitting new tickets, intended for information to users regarding what information to submit and similar.
  • Option to ignore rendering of 'CamelCase' words as missing pages (only display plain text).

Blog Settings

  • The 'number of posts on front page' is a restriction to limit how many posts to show (max) when listing posts with full content. Same setting is used in category and author listings, as well as RSS feeds.
  • 'Blog sidebar information' is wiki markup that gets inserted at the bottom of the sidebar, and can be used for additional information of any kind.

Ticket System settings

The Ticket System provides a number of features for assigning various properties to a ticket, and for most projects these classification features are very useful when trying to keep control of what requests are received, what needs to be done, what subsystem does it relate to, what version, and how do we rate it with regards to importance and priority.

  • Components -- Useful for dividing a project into sub-modules to enable reporting on issues for just a part of the solution.
  • Priorites -- Default lowest, low, normal, high, highest but can be changed to whatever is suitable.
  • Severities -- Default trivial, minor, major, critical, blocker.
  • Ticket Types -- Ticket Types is useful for allowing the general Ticket system handle other information than just bugs. Default is defect, enhancement, task but other such as support can be added depending on project.
  • Versions -- For classifying a ticket issue to a specific version of the software. Note that this is a seperate entity from any versions found in the repository - but naturally the Versions here should be named to correspond to some software property; 1.0, 2.0}} or {{{0.x, 1.x or aplpha, beta, release and similar.

If a property has no defined variables, it will be removed for view for all users accessing or creating tickets.

Using properties on tickets allows users to create very specific reports for querying the ticket system. See HelpUser/Tickets and HelpUser/Reports for more information.

Roadmap and Milestones

The Milestones defined in the Roadmap are administrated through the Roadmap module and not in "Admin". Click on a default milestone to edit or delete it, or use "Add new milestone".