Project

This is the main and important item for TeamForge. For projects we support following fields.

• • id, title, description, date created, hierarchy path, parent project id, path and locked

The CollabNet service is responsible for project related operations.

Forum

Teamforge repository can have forums and inside a forum we can find topics and posts.

For a forum we support following fields.

• • id, title, description, last modified by, created by, modified on, project id, path, footer, forum type, list name, reply to, prefix, created on, folder id, list enabled, private forum

Topic

For a topic we support following fields.

• • id, title, description, last modified by, created by, modified on, project id, path, parent folder id

Post

For a post we support following fields.

• • id, title, content, created by username, created by, created on, forum id, topic id, reply to id, status, project id

The Discussion service is responsible for forum, topic and post related operations.

Document Folder

Teamforge repository can have document folders and inside a document folder we can find documents and document reviews. For document folders we support following fields.

• • id, title, description, created by, last modified by, parent folder id, project id, modified on, path, created on

Document

For a document we support following fields.

• • id, title, description, file name, created by, modified by, folder id, file size, file url, project id, project title, project path, folder path, folder title, locked by, mime type, modified by full name, date created, modified, current version, version created on, version comment, version created by, version created by full name, version id, version number, status

Document Review

For a document review we support following fields.

• • id, title, description, version number, date created, due date, end date, optional reviewers usernames, required reviewers usernames, status

The Document service is responsible for document folder, document and document review related operations.

Release Package

Teamforge repository can have release packages and inside a release package we can find releases and release files. For release package we support following fields.

• • id, title, description, created by, last modified by, created on, modified on, parent folder id, project id, status, path

Release

For a release we support following fields.

• • id, title, description, created by, last modified by, created on, modified on, parent folder id, project id, status, path, maturity

Release file

For a release file we support following fields.

• • id, title, description, file name, file size, date created, content id, folder path, mime type, package id, package title, project id, project path string, project title, release id, release title

The Release service is responsible for release package, release and release file related operations.

News Posts

For a news post we support following fields.

• • id, title, body, created by user name, project id, project path, project title, created by full name, created on

The News service is responsible for news post related operations.

Planning Folder

Teamforge repository can have planning folders and inside a planning folder we can find artifacts. For planning folder we support following fields.

• • id, title, description, release title, created by, last modified by, path, parent folder id, project id, release id, created on, modified on, start date, end date, capacity, status, status class

Artifact

For a artifacts we support following fields.

• • id, title, folder title, description, planning folder id, planning folder title, project id, project path string, project title, folder id, folder path string, folder title, status class, status, category, estimated effort, actual effort, remaining effort, artifact group, assigned to full name, assigned to username, auto summing, reported in release id, reported in release title, resolved in release id, resolved in release title, has children, children id, close date, customer, modified date, points, priority, submitted by full name, submitted by username, submitted date, tracker icon, version, child dependencies, parent dependencies.

The Planning Folder service is responsible for planning folder and artifact related operations.

Project Page

Teamforge repository can have project pages and inside a project page we can find page components. For planning folder we support following fields.

• • id, title, description, created by, modified by, path, created on, modified on, parent folder id, project id, display position, free form, visible

Page Component

For page component we support following fields.

• • id, title, component type, created by, last modified by, path, created on, modified on, settings, folder id, visible, version number, content

The Project page service is responsible for project pages and page component related operations.

Task Group

Teamforge repository can have task groups and inside a task group we can find tasks. For task groups we support following fields.

• • id, title, description, created by, last modified by, path, modified on, created on, parent folder id, project id, status, overdue tasks, status roll up

Task

For task we support following fields.

• • id, title, description, created by username, accomplished, assigned to full name, assigned to username, created by full name, created by user name, start date, end date, estimated hours, required hours, folder id, folder path, folder title, included weekends, issues, parent folder id, planned, priority, project id, project path, project title, status.

The Task service is responsible for task groups and task related operations.

Tracker

Teamforge repository can have trackers and inside a tracker we can find artifacts. For trackers we support following fields.

• • id, title, description, created by, last modified by, icon, last edited by full name, last edited by user name, last edited date, created by, created on, last modified on, parent folder id, path, project id

Tracker Artifact

For a artifacts we support following fields.

• • id, title, folder title, description, planning folder id, project id, project path string, project title, folder id, folder path string, status, category, estimated effort, actual effort, remaining effort, artifact group, assigned to full name, assigned to username, auto summing, close date, customer, modified date, points, priority, submitted by full name, submitted by username, submitted date, version, child dependencies, parent dependencies.

The Tracker service is responsible for trackers and artifact related operations.

Repository

Teamforge repository can have SCM repositories and inside a repository we can find commits but we are not supporting commits. For repositories we support following fields.

• • id, title, description, created by, last modified by, created on, modified on, parent folder id, project id, status, path, repository path

Wiki

Teamforge repository can have wiki pages and we support following fields on wiki pages.

• • id, page name, version crated by, version number, date created