Create a tracker artifact

Create a tracker artifact whenever you need to report and track a bug, feature request, support request, or other type of issue.

Individual tracker entries are referred to as tracker artifacts, or just artifacts.
  1. In any tracker, planning folder or teams view, click Create Artifact and select the tracker in which you want to create your artifact. By default, your new artifact is created in the tracker, planning folder or team you are currently looking at.
  2. Answer the questions posed by the required fields.
    Note: Different trackers will have different combinations of fields to fill out, depending on what the tracker administrator has set up.
    1. Provide a Title and Description that summarize the issue or work item in a few words.
      Tip: Descriptions help users learn how best to provide the information you want from them. To maximize your chances of getting useful data, make your description as informative as you can.
      Artifacts support @mentions: Artifact description and comments now support @mentions and users called out via @mentions are added to the monitoring list. Include usernames with "@" as prefix (for example, @mphippard) to add users to the monitoring list.
      Note: Users called out via @mentions must have "Artifact View" permission to be added to the monitoring list.
    2. Now project members with CREATE/EDIT permissions can also create new tags or add existing tags, if required from Create Artifact page. Tags creation from Create Artifact page enables you to create tags on the go and overrides the limitation of creating tags only from the Tags page. However, you cannot rename or delete a tag from Create Artifact page. Click the button next to Tags field to get the list of tags mapped to your project. You can add up to a maximum of 10 tags to any artifact and a message is displayed if you try to add more than 10 tags. If the entered tag name is not available already, a context menu Create a new tag shows up for you to create a new tag with the desired tag name.
      Note: Wherever the tag widget is not applicable, the associated tags are displayed as read only tags. For example in View Artifact page.
    3. For Priority, select a value that expresses the importance or urgency of the work you are describing.
    4. Assign the artifact to a team by selecting a name from the Team list.
    5. If you want to assign it to a specific project member, choose a name from the Assigned To list. This lists displays the names of all the project members, irrespective of the team you may have selected in the previous step.
      Note: From 17.8 release, TeamForge is configured to send HTML emails to users assigned to and users monitoring the artifact you create or update. For more details, see HTML emails.
      Note: If your project administrator has configured the tracker to automatically assign artifacts to project members, you can skip this step.

      Reassigning artifacts can now be done in no time. Use the links under the "Assigned To" field to quickly unassign the artifact to "None", reassign the artifact to yourself or to the previous assignee. You can also click the "Re-assign" icon to search and reassign the artifact to any other user.

    6. Select the planning folder that the work belongs to from the Planning Folder list.
  3. Record any other information that may be appropriate. For example, if your project is using a Scrum-based methodology, your project manager may have provided a Points field to track estimates of relative effort.
  4. Add a file attachment, if appropriate.
    Note: When creating or editing an artifact, you can drag and drop any number of files with their overall size not exceeding 25 MB in the Attachments field. You can also select multiple files using the Browse button. Make sure that you add only files of restricted file types. For more details on attaching restricted files types, see the section Restricting specific file types as attachments in New Features in TeamForge 17.8.
  5. Save your changes.