Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Guidance on using stories VS tasks

We are an application maintenance team and primary work on BAU support and implementing minor enhancements. We are not a software development team.

We use Kanban boards and not Scrum boards.

Could you please explain the difference between a JIRA story and a task and how they should be used.

Example 1 - Work item "Create report A". Should this be a story or a task?

Example 2 - In EPIC "Upgrade Application A to V1.1", there is a work item "Regression test Report A". Should that work item be a story or a task?

I'd appreciate examples of how you've used epics, stories and tasks in your JIRA project

Thank you

Dan

 

 

3 answers

2 accepted

3 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 03, 2022

Technically, underlying Jira behaviors treat tasks and stories the same. There is no difference, it is simply a name. It is left to the users to decide when they use one vs. the other. 

Stories are traditionally associated with agile methodologies and especially scrum.   But you can just as readily use tasks.

Thank you Jack

Like Jo likes this

@Jack Brickey - if I wanted to keep things as simple as possible I'd tend to either only use story or task with sub tasks if necessary. A purely semantic differentiation could be to use story only for user stories in software development and task for (administrative) ToDos in any kind of project (like setup software xyz or organize a workshop). What do you think?

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 26, 2023

It really is personal preference but indeed for a true Software project I use Story for use cases for desired functionality and reserve tasks for issues that don't translate to modifying the product. For example - Review document would be a task.

Like YOWfactor likes this
2 votes
Answer accepted
Peter DeWitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 03, 2022

@Daniel Tan , There are so many ways of using this issue types. The crappy answer is that you can use them for whatever you want. However, here is a bit of advice from my years working:

task - something that takes minutes to complete

story - something that takes hours to complete

epic - the equivalent of a project containing stories and tasks. Takes days to complete.

-pjd

Thanks Peter - I'm always in favour of pragmatic solutions :)

Like Jo likes this

Well, time criteria in defying the type of your work does not seem credible. Why would we even spend time on creating a new task that would take minutes to complete?

(User) stories are for feature and functionalities of the software being developed, bug reports are for bugs, tasks are for other project works, such as documentation, planning, reporting, prepare release, architectural design, database design, etc  Some of those can be subtasks to bug reports and user stories.

Developer tasks, user stories, product bugs.

(User) stories are for feature and functionalities of the software being developed, bug reports are for bugs, tasks are for other project works, such as documentation, planning, reporting, prepare release, architectural design, database design, etc  Some of those can be subtasks to bug reports and user stories.

Developer tasks, user stories, product bugs.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events