Redmine issues are the work records a project team uses for bugs, support requests, tasks, and follow-up items. Creating one from the project Issues screen puts the request under the right tracker so the team can triage it from the same list as the rest of the project work.
The issue form belongs to a single project. Redmine applies the project's enabled trackers, workflow rules, role permissions, priorities, and assignable members before it saves the record.
Start with a project where issue tracking is enabled and your account can add issues. Save a short subject, a useful description, and the fields your team uses for routing, then verify the issue page and project list show the same values.
Related: How to create a Redmine project
Related: How to create a Redmine tracker
Related: How to add members to a Redmine project
https://redmine.example.net/projects/field-service/issues
Replace the hostname and project identifier with the values from your Redmine site.

Trackers control the available fields and workflow for the issue. Use the tracker your project uses for bugs, support requests, tasks, or changes.
If the expected assignee is missing, confirm the user is a project member with a role that can receive issues.
Related: How to add members to a Redmine project
Redmine should show an issue ID, Open state, tracker, status, priority, assignee, and description on the saved issue page.
