I'm currently organizing a software project via Jira on my own. Right now I'm the only one who is developing on that project. However it is possible that more people will join the team in the near feature.
I'm now wondering how to deal with stories and tasks. I/we don't using Scrum but a Kanban board with three columns (backlog, in progress, done). There are a lot of epics and tasks to do and I just included a new issue Type named "story". How would you handle the state of the stories?
For example: There is a story called "As a user I want to print the document" and a couple of tasks which are related to that story like "add printing button to UI" for example. When starting a task, I will move the card to the "in progress" column. The Question now: Should I move the story on the board to "in progress" too? Should we display stories on the board in general? It's feeling a bit like doing redundant organization since I/we have to check the stories every time tasks changed "by hand" (checking "are all related tasks done?" If yes then we have to move the story too). Or should I avoid using the concept of stories in general?
I hope it's understandable what I'm trying to describe.