Frage zu Issue vs. User Story

[Frank Borchart]

Hallo in die Runde,

bei den wundervollen Beschreibungen der einzelnen agilen Artefacte bin ich von der Beschreibung einer User Story über einen Text auf den Beitrag gekommen, wie man User Stories in Jira dokumentiert - dort allerdings ist von "User Story" keine Rede mehr, sondern von Issues. Kann mir jemand nochmal den Zusammenhang bzw. die Unterschiede erklären?

Vielen Dank

[Bert Dombrecht]

Hallo, und wilkommen, Frank,

You could consider 'issues' as the smallest artefact in Jira.

An issue can be of a certain type. The 'User Story' is just one of many issue types.
An issue can also be a of the type Bug, Incident, Epic, etc.

Issues can also be linked together in a parent-child hierarchy.
For example: an Epic grouping multiple User Stories. Or a Task with multiple sub-tasks.

So, when we are talking about the smallest artefact (of any type) we refer to them as issues.

If you are talking about a hierarchical structure of issues, you could consider a User Story as the smallest chunk of work to deliver an Epic.

Hope this helps and sorry for responding in English, mein Deutsch ist nicht so gut :-)

[Franz Reichard _Communardo_]

"Issue" ist einfach nur ein "Vorgang". Ein "Issue" kann z.B. ein Bug, ein Feature Request, eine User Story, ein Task, etc. sein. Issue ist also nur der Oberbegriff.

[Mayuresh Sakharape]

Every User story in JIRA is an issue but not every issue is an User story. Issue is a basic building block and User story is an certain representation of issue. So you can have an issue with any any name like User story/defect/bug/task/sub-task.

So issue is an interface in java and User story is an class which implements this interface. Its not exactly same but just an analogy.