Back to Forum

Story vs Task and Bugs

Last post 01:38 pm June 27, 2017 by Timothy Baffa
1 reply
Ashley Lee
02:55 am June 24, 2017

How do you differentiate between a story vs task or bug in JIRA? Do Would love to hear your thoughts and guidelines!

Timothy Baffa
01:38 pm June 27, 2017

In my experience with Jira, the Issue Type field can be used to differentiate between stories, tasks, and bugs.   To me, each story should be customer-facing (end-user value), and tasks should be created that are needed to meet the story's acceptance criteria.   Even when tasks are technical in nature, you can create them under a story that captures the value being delivered.

 

I have also seen good practices where "Bug" items are either linked to the original story, or to a "legacy" placeholder-type story for bugs that are latent or reflective of technical debt.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.