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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue breakdown in Jira


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.



0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events