Is it okay to use story and task interchangeably?

[Vandana Khairnar]

How can one differentiate between a story and a task? In my organization, agile transition is at very initial stage and people are a bit confused while creating issues in backlog in JIRA. What kind of issues can be considered as a story and what kind as a task? Please provide some opinions.

[Jack Brickey · Accepted solution]

Yes certainly you can use them interchangeably in the Jira world as they behave the same with only the name being unique. With that said, IMO not using them interchangeably is best. I like to use Story when following agile concepts. Specifically, I like to use story when I write an issue summary like this example - As a shipping specialist, I would like a button to easily track the status of a shipment. While a Task tends to be a specific declaration of “go do this”, for example the summary might be - Change the shipment tracking button to blue.

Of course this is all opinion and personal preference.

p.s. Lots of Agile stuff out there with lots of variation. Here is something you might find of interest - https://www.mountaingoatsoftware.com/agile/user-stories