I already read: How to map user stories into tickets?

But I still have difficulties understanding how I exactly should use a ticket system, especially in the case of tickets for new features.

Let's assume the project is at a point, where we know what we have to do, but didn't start any coding. The first thing I want to do now is to bring all the requirements into the tickets system as tasks.

What would a Task-Ticket look like?

Is it a user-story like: As a guest I want to be able to register myself with the site or should I split them into tickets/tasks like Create a registration page/form, Send an email to to the user when registered. Is it a good practice to use user stories, or what is the best way to go?

If this information in relevant: We're going to use the github issue tracking system.

I already read: How to map user stories into tickets?

But I still have difficulties understanding how I exactly should use a ticket system, especially in the case of tickets for new features.

Let's assume the project is at a point, where we know what we have to do, but didn't start any coding. The first thing I want to do now is to bring all the requirements into the tickets system as tasks.

What would a Task-Ticket look like?

Is it a user-story like: As a guest I want to be able to register myself with the site or should I split them into tickets/tasks like Create a registration page/form, Send an email to to the user when registered. Is it a good practice to use user stories, or what is the best way to go?

If this information in relevant: We're going to use the github issue tracking system.