nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

what is the difference from a user perspective between an epic and a story issue type?

Flavius Nopcea

is there a difference except the name of the issue type?

thank you

Accepted answers

Radu Dumitriu

Please print this : http://agile101.net/wp-content/uploads/2009/08/the-difference-between-themes-epics-user-stories-and-tasks1.jpg

All comments

Flavius Nopcea

can aynone give an answer pleasE?

Radu Dumitriu

Please print this : http://agile101.net/wp-content/uploads/2009/08/the-difference-between-themes-epics-user-stories-and-tasks1.jpg

George Carvill

I think there should be this kind of a difference:

https://answers.atlassian.com/questions/87277/epics-beget-stories-and-stories-beget-subtasks

Lucas Molenaar

imo an epic is nothing more than a very large story. When broken down in stories (backlog grooming) an epic can be deleted

George Carvill

As with so much, it probably depends on how your group works. While I understand the idea of deleting the epic when it is all chopped up into stories, many may want to keep the epic as a reference to all the related stories. Even if dev doesn't care any more, those in marketing or documentation or support may well like to be able to see the high-level idea (Epic) and the pieces that went into it.