CODEWITHSUNDEEP
taskjirascrumkanban
MilkTea027
MilkTea027

Reputation: 301

Should technical stories in Jira be stories or tasks?

I am preparing a Kanban board for my team, and under an Epic, you can create three different kinds of issues: Stories, Tasks, and Bugs.

enter image description here

I discussed with my team whether a Technical story should be a story under Epic or a task under Epic.

Their point being is a story is more on business-related "user story" (not the technical story), and that technical story should fall under Task with subtasks.

As for me, I've gotten used to Scrum boards in different platforms having a technical story as the story, and we create tasks under it.

The subtask of this so-called technical story will contain the following:

Whether we create it as a task or a story, I think the process will be the same anyway, but what would you guys recommend we use?

Upvotes: 1

Views: 1239

Answers (1)

Ranga Lakshitha
Ranga Lakshitha

Reputation: 306

This depends on how you use it.

Normally, A Story: more detailed functionality

A Task: is smaller technical improvements or backend work.

Recommendation: Choose based on your team's understanding and workflow. Use retrospectives to adjust your approach based on what works best for your team. The goal is clarity and efficiency in your team's processes.

Upvotes: 0

Related Questions