Everything depends in your scope and the way you handle your project.
There is not just one path where you can go and both are totally great and valid.
As per my own experience, user story helps you estimate your project, for example, you can have a “crud” as a “user story”:
User Story: “As an admin, I would like to create new users and edit their information and control their access”
Tasks: “Cread, Read, Update, Delete, users”
So it´s a differente way to see things, you can gather client requirements with user stories and then estimate your project.
If you want an example of user stories in leantime, I´ll try to do one
“As an admin, I would like to create new users and edit their information and control their access”
You can give estimated time to each subtask, and user stories help stakeholders to understand what are we building, since it´s a more “normal way to say things”.
Hope this helps.