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; } } }

User story vs. New Feature

Eugene

The question is about types of issues.

When it's better to use User Story and when to use New Feature. What's the difference?

And can User Story contain several New Features or only Tasks?

Do you link them or how you see the mapping to all the tasks associated with a User Story?

I just want to understand which types of issues to leave in JIRA and in what cases I have to use them.

Thanks.

Accepted answers

Norman Abramovitz

The short answer is whatever makes sense to your team. The issue types are just labels. You can create additional labels for issues. It is your team's definition of those labels that matters. There is no reason why an 'User Story' cannot have both 'New Features' and 'Tasks' related issues.

All comments

Norman Abramovitz

Eugene

Norman, thanks for taking time for the reply. Thas makes sense.

But ...

We use rapid board (kanban) in our process. And if the User Story will contain both New Features and Tasks how not to lost them all while resolving? It's good to create a Task and then related subtasks, then it's attached to the view task page and one can see all subtasks. How to do this in case of User Story or New Feature? (So under New Feature I can see the related tasks and progress of these tasks?)

Norman Abramovitz

You use issue linking to maintain the relationships. Maybe reading this previous answer will help you understand better. It is the section about breaking down stories that relates to your question.

https://answers.atlassian.com/questions/72394/manage-epic-stories-in-jira-greenhopper

So if I understand your example

User Story 1

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

agile