Issue breakdown in Jira

[Dharmesh Barot]

Hi,

Would you please share some ideas on how you breakdown issues in Jira to make activities like visualizing work items, estimation, capacity planning easier? 

Not looking for addons yet, so wanting to understand how OOTB Jira could be used.

Let's say you are building an ecommerce system. 

Epic = Product Detail Page (PDP)

User Stories could be (going to be brief to give you some idea)

1. Display product information
2. Display product inventory status
3. Display product variations
4. Display product images
5. Display product pricing
6. Submit product questions from PDP

Assume there is an integration between Ecommerce system and ERP to pull in product attributes, pricing, inventory, and images

How would you break these down further to give details to the engineering team?

E.g. Work that needs to be done on the frontend, backend, integration, etc. to be able to visualize technical sub-tasks for the engineers, technical stories if any, and get estimates, so that we can plan capacity for the team.

Would you make something like "Get product attributes from ERP" as a techical story and link to 1. Display product information OR a sub-task of that user story?

In Backlog planning view of a Scrum board the sub-tasks are not visible, so team finds it cumbersome to find all the sub-tasks for review and estimation. Without sub-tasks it becomes difficult for QA to know all the issues that need to be completed to test a user story.

Please share your way and some ideas of what worked for you as well as what to stay away from.

Best,

Dharmesh