The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to manage Epics in a support project?

Thomas M Abraham
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!
December 28, 2023

I work on a native mobile app support project. I have created the main features of the mobile app as the Epics. The problem that I have is that these Epics are now never ending Epics. Every release/sprint I create enhancements under these Epics and am not able to close these Epics due to the never ending enhancements/updates.

 

Is there a better way to manage/create epics in a support based project?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Trudy P Claspill
Community Champion
December 28, 2023

Hello @Thomas M Abraham 

Welcome to the Atlassian community.

One alternative is to create time-boxed Epics. You could create Epics like "Enhancements during Q1 for Functionality A", and create under that Epic the enhancements you intend to make in Q1 for that functionality. Then close the Epic at the end of the quarter, moving any incomplete issues to the next quarter's epic.

Or, you could make Epics that are functionally limited to 1..n enhancements that you plan to make, and close the Epic when those specific enhancements are completed.

 

What Jira functionality are you trying to leverage by grouping these changes into Epics? That could help us come up with alternate suggestions.