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

Guidance for single stories that don't fit into the quarterly epic?

I'm relatively new to JA. Since epics need to be contained to one quarter/program increment, I frequently find scenarios where my teams have just one story, maybe two, that are needed in the next quarter. Creating an epic just for one story is not scalable at our volumes, creates extra levels of administration overhead, etc. What is the guidance for when this occurs?


For example - we expected to upgrade Database 123 in Q1. We finished everything but one story, which will wrap up in the first or second sprint of Q2. Is it really necessary to create a whole new epic just for this one story?

1 answer

1 accepted

1 vote
Answer accepted

Hi @Alissa Quick 

Assuming you are syncing between Jira and Jira Align bi-directionally, you can the Split functionality in Jira Align to Split your epic.  To locate this functionality, open the Epic you will need to split so you can complete work in the next PI.  Make sure your stories are actioned.  On the right side of the Epic, locate the + Show All link and click the link.

Split Epic.png 

Additional options will open.  Click the "Split" link.  A window will open to show the new Epic.  Jira Align will automatically do the following:

  • Name your new Epic the same as your original epic and add "(Split Part 2) 
    • It will also add "(Split Part 1)" to your original epic.
  • Copy the Summary over to the new epic and add "(Split Part 2)"
    • It will also add "(Split Part 1)" to your original epic summary.
  • It will move your new Epic to the Backlog, however from this screen you can assign it to the next PI.
  • Automatically move any Stories not accepted to the new split Epic.
  • All program, team, project, etc. information will be copied to the new epic.

Once you click Split, your new Epic, and all stories not accepted, will either show in the backlog or in the PI you selected.

Screenshot 2023-03-27 at 1.43.41 PM.png

This is helpful! However, it is still extra work for just one story and with so many epics to work through it becomes tedious. What are the implications if I don't split the epic and leave the last story under the original epic?

Great question.  The thing you have to keep in mind, is that if you don't split your Epic, your reporting will not be accurate if you have a story that is misaligned (assigned to a sprint that is not associated with the PI) to the Epic's PI. 

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events