Skip to main content
Version: TeamForge 23.0

FAQs on Search

What resources can be searched on a TeamForge site?

The resources that show up in search results depend on the context in which you are working.

Here is a summary:

ToolSearchable resources
ProjectsProject id, title/description, created by, project status
Project categoriesTitle, description
Discussions
  • Web UI: author, subject, content, attachment.
  • Email: we index the original email after we process it.
  • Topics: author, title and description.
  • Forums: title, description, author.
Documents
  • Document folders: title, description
  • Documents; version comment, title, status, description, the attachment itself (all versions), authors
SCMCommit message, title, author
Tracker
  • Tracker title, description, author
  • Artifacts: title, group, category, customer, status, description, authors, tracker, all text flex fields, single-select fields, multi-select fields
  • Artifact attachments: the attachment itself and comments
NewsBody, title, author
File Releases
  • Packages; title, description, author
  • Releases: title, description, author, maturity, status
  • Files: description, filename
TasksTitle, description, authors, planned
UsersUsername, full name, email, status, details
Pages
  • HTML components: title, content
  • Subpages: page title, component title
WikiContent of wiki page, using wiki syntax

Occasionally, an exceedingly large or complex document causes the search indexing service to abort.

This is typically when all searches in TeamForge return an exid to the user.

Check the server status page and see if the search server is listed as anything other than OK. If it is not OK, then you should restart the search service by logging into the TeamForge application server as root and issuing the following command:

/opt/collabnet/teamforge/james/james-/bin/phoenix.sh restart

Check the server status page again in TeamForge and ensure that it shows a status of OK. If it shows OK, then searches should now work, and the site will slowly catch up on any indexing requests that were logged while the service was down. If you continue to get exids returned for all searches even with an OK status, then you probably have corrupt search index files.