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

What is the best way to break down issues in a large project?

Alberto Reig
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 04, 2023

My team is working on a large software project, and I am struggling to find the best breakdown according to Jira's best practices. I previously worked with Azure and this is my first project using Jira.

I broke down the project into three levels: wide software features (1st level), these broken down into more specific software features (2nd level), and each of these divided into small individual functions to implement (3rd level). For these, I am using epics, stories, and subtasks respectively. I already have many stories within each epic, so for the sake of tidiness I need these three levels. 

Due to the size of the project, epics and stories are big issues which span multiple sprints, whereas subtasks are issues that my team can develop purely within a single sprint. For sprint planning, I would need to assign subtasks under the same story to different sprints, but it seems subtasks are not meant to work this way.

It probably has something to do with me not making a proper use of Jira. What would be your proposal for my project breakdown?

1 answer

0 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 04, 2023

HI @Alberto Reig ,


You may want add another level and bring everything up one by using initiatives.


Here's an article from Atlassian:,any%20of%20the%20epics%20themselves.


This will allow your stories which would be your current sub-task to fit into sprints and assign each of them to different sprints. Stories usually should fit within the sprint. 

Then have sub-task used to break down the more complex stories if needed from the team.

Alberto Reig
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 05, 2023

Thanks @Benjamin !

Is there any way to include initiatives in the free plan?

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events