It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
This question is in reference to Atlassian Documentation: Working with Issues
Whats the difference between an issue and story?
My though is that issue can contain several stories.
And both issue and story can contain several subtasks?
Is that correct?
No, an issue is "something that needs some attention". Issues are done at the same level as Stories.
The heirarchy you are looking for is Epic -> Story -> Subtask. But there's nothing to stop you having different types of stories or subtask, and issues would be treated as though they're at the story level in the heirarchy (unless you add "issue" as a sub-task type)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's what I just said. I don't know what you mean by "it's an issue or story"? An issue of issue type called "issue" behaves the same as an issue of an issue type called "story".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.