Issues

Open the issues tab. Here you will start creating issues for things that need to be done and what you are doing. From studying documentation or watching tutorials to adding features. When creating a new issue, give it a short title that well conveys the change or feature to be added or the bug to be fixed or the meeting to be held. In the description, add a detailed description depending on what the issue describes, for example, if it's a new feature, describe how it would look like when it works, and also add acceptance criteria, which are individual points based on which it can be said whether something exists and works or not.

Assign the issue to its creator (or divide it among the team members according to what each one will do). Also, assign it to a milestone it belongs to (usually the one that is currently ongoing or just starting).

Finally, you can also assign labels to it, which makes it easy to sort or view them later, to know what you're dealing with. You can create all sorts of labels depending on what you want and how you want to manage things. As a suggestion, you can add labels like: critical (if something needs to be done immediately), feature (if it adds something new), server (if it's related to the server and the server is in the same repository as the client), client (if it's client-related), bug (if it's a bug that needs fixing), design (if it's related to designing something), plan (if it's related to planning or, for example, meetings or learning), metaissue (if it's an issue related to managing other issues).