Redmine trackers separate issues into work types such as bug reports, feature requests, support tickets, and maintenance tasks. A tracker controls the default issue status, the standard and custom fields shown on issue forms, and the workflow rules that let each role move issues through the lifecycle.
The tracker is a site-level administration object. Projects must enable it before users can select it from the New issue form, and workflow rules must exist before the tracker can support normal status changes after issue creation.
Start with a short tracker name, a default status, the fields that users should fill in, and the projects that should receive the tracker. Use an existing issue custom field when one already captures the extra value, or create the field first when the tracker needs a new dropdown, date, text, or user field.
https://redmine.example.net/trackers
Replace the hostname with the URL for your Redmine site.
Copy workflow from gives the tracker existing status transitions at creation time.
Related: How to create a Redmine custom field
Adjust the matrix when the copied workflow allows too many or too few status changes.
Related: How to configure a Redmine workflow
Trackers are not visible in a project until the project enables them.
Related: How to create a Redmine project
Related: How to create a Redmine issue