Stories vs tasks in our sprints

Question

Fellow Atlassians! I am new to Jira and Scrum so please be gentle...

I have a backlog full of stories ("As an instructor, I want to enter attendance."). During backlog refinement we assign story points to those stories, as well as break them down into smaller actionable tasks ("Add attendance user access to permissions table").

Now it's time to move the items into the sprint. Do I put both the tasks and the stories in the sprint? The actual work is being done in the tasks, but from what I've read the stories need to be what get accepted, so it sounds like we need both in there. Do the stories move to In Progress as the tasks do?

Thank you all :)

Thomas Schlegel · Answer

Hi @leonardonogatz ,

stories should be finished within one sprint. I would say, long lasting stories are epics. These are independent of the sprints duration and can last forever if you need them to.

leonardonogatz · Answer

I found this post trying to clarify my understanding about my work board. I thought at first like Greg, that in subtasks will be easier to the sprint have and end, a visual end on JIRA. But sometimes finish subtasks can no end a story, and the sprint is about a story (where we estimate). 
If I understand correctly, @Thomas Schlegel the end of a sprint should end a story(s)?
It is hard for me understand it cuz in my job we depends a lot of a third part work, sometimes the story never ends and I can't figure out where is the mistake. (I am just a developer but sometimes it bothers me).

Thomas Schlegel · Answer

The tasks are independent of their stories within the Active-Sprint-Board. That means, you can move a sub-task to any other column, and if the last subtask of a story is done, Jira asks you, if the story should also be moved to done.