database design suggestions

i am creating a minimal issue tracker application, the user flow is as follows: - user signs in (passwordless auth) - creates a username (if signing in first time) - creates a project - creates custom priority levels - creates custom statuses - creates an issue - assigns, the custom created priority and status - invites other users to project - assigns the user roles - edits the issue to assign it to a user i have the following database design as an initial iteration, what suggestion do yall have to make it more robust and scalable
No description
0 Replies
No replies yetBe the first to reply to this messageJoin
Want results from more Discord servers?
Add your server