Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Aaron Smith
916 PointsDo user stories stand alone as complete backlog items, or are they typically accompanied by other info like a title?
Just thinking about how a team might efficiently and consistently refer to user stories in the backlog without making up shortened versions of them, like "the progress bar one". Do user stories get titles of any kind, or tags to categorize them in any way?
2 Answers
Brian Jensen
Treehouse TeacherGreat question Aaron Smith! The course doesn't cover it, but most teams would use a tool such as Jira and Trello to keep track of tickets. Your thinking is correct, in those apps it would be very common to treat user stories as complete backlog items each getting a unique title and in most cases a priority tag and department tag such as client, server, infrastructure etc...
Kari Brooks
Treehouse StaffA complete backlog item typically includes:
The title: a short, scannable label (e.g., "Progress bar on course completion").
The card/ticket number: Tools like Jira will auto-assign a number that precedes the title (e.g., MA-175: Progress bar on course completion), which is often the primary identifier in commit messages, PR titles, changelogs, and everyday conversation.
The user story: the formal statement that lives in the description field. The "As a [role], I want [goal], so that [benefit]" format is just the story itself, not the full backlog item.
Acceptance criteria: the specific conditions that must be true for the story to be considered done. Without these, "done" is subjective, which causes problems at QA time. Often these are framed in a Given/When/Then format.
Additional fields: these vary by team but can include story points, priority, labels/tags, links to other tickets or an epic.