what is the different between task and story in software project

[Sapir Michaeli]

what is the different between task and story in software project

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

It's whatever you want it to be really.  Jira Software has three layers

• Epic
• Base level issue
• Sub-task

Stories are typically a type of base-level issue, and a lot of people define "tasks" as existing as sub-task types.  But you can use different names, have many types, and you will find many people have tasks at the base-level, rather than sub-task.

If you've done that, then your question is actually "what's the difference between issues and sub-tasks, and the answer to that is that "sub-tasks, whilst looking a lot like issues, are not independent, they are a fragment of their owning parent issue".  This means there are things about them that they have to take from their owner - they move into sprints as part of their parent, they can only belong to the same team as their parent, they can't have different versions, you have to infer what Epic they belong to by looking at the Epic of the parent, they take their security from the parent, and a few other things.

[Dave Mathijs]

Hi @Sapir Michaeli welcome to the Atlassian Community

Although anyone can have their take on the differences, I'm referring to this article:

Difference and use cases of Jira issue types: Epic vs. Story vs. Task in Jira

[Sapir Michaeli]

I already read it. 

still not clear to me. 

task - should end in one day

story - may end in few sprints

I will glad to get more example and explanation

thanks.

[Dave Mathijs]

A task and a story are just names of issue types within Jira. An issue type is a work item. You can name and use it anyway you want. If you're not familiar with the terms user story, sprint of scrum, no worries! Just use Task as issue type in a project.

[Nic Brough -Adaptavist-]

That is not right.

• Epic - should end when it is done (meaning all the stories in it are complete) - usually made up of many stories, and rarely completed within a single sprint.
• Sub-Task (task) - should end when it is done, as part of the parent issue.  (Nothing wrong with aspiring to complete them in a certain time-frame, but it's not wrong to have them take minutes or days)
• Issue (Story) - should be started and completed within a single sprint.  If an issue "spills over" into the next sprint, it is a massive red-flag that your team has failed to deliver for some reason, and you should be discussing what went wrong and how to avoid it happening again in future sprints.