I am learning about the agile/scrum process, and currently using it for a 6 month software project at my university. My team is using Jira.
I am starting to get confused between the difference between "tasks" and "stories".
I had thought that "story" aligns with "user story", which was one of the mechanisms we used to define our requirements. Each requirement on our project has a user story associated with it. I was told that the agile process is different because it keeps the "user" perspective in mind while developing. It made sense in my mind that a user story maps to a "story" in Jira. However, I read that in Jira Agile there is no difference between a task and a story.
My team has been creating subtasks for every story, but I was told this was wrong, and that our stories are too large and need to be broken down. For example, one story was "I want to be able to sign up for a free account to use the system". This obviously involves many subtasks. We ARE creating subtasks under the stories, but we were told the story itself is too big. How would I "break this story down into smaller stories"? A user wouldn't have a story about something technical, like "Set up a database server". I was told to make stories like "as a developer, I want to install a database server so that I can store new user information". This doesn't make sense to me, because we were previously told not to consider a developer as a user.
So, my question really is why is it wrong to create a story that consists of many subtasks? Is this just a choice that the team makes, or is there actually use cases for the difference between a task and a story?