Loading Profile...
Will banana scrum assign ID to story?
We find that referencing stories by an immutable ID is important. A (short) URL would be useable, though a meaningless ID (number) is often helpful.
I don't see how to reference a story from outside the tool (given that it can be renamed and the reference must still be valid).
I don't see how to reference a story from outside the tool (given that it can be renamed and the reference must still be valid).
I’m evaluating
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?We didn't see a need for an ID as a separate field etc. If a user wants to enter some codes in the user story (by using for example square brackets like this: "[1.2.44] As a user I can see a list of entries") they can do it within the current functionality.
User stories were meant to be simple as an idea so their implementation should also be as simple as possible. Hence, we would rather not bloat the interface with additional fields if what they would bring could be achieved easily within the current context. -
Inappropriate?I think jwb is more looking for a way to publicly and/or anonymously access user stories, which would make sharing them easier. -
Inappropriate?This is something we definitely have on our backlog, as we foresee this tool could be used for open projects where backlogs are public. However I won't get into details just yet.
EMPLOYEE
