Best practices to manage Epics

roy adams
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!
June 18, 2024

In Jira,
The backlog view won't show Epics (unless you click the epic tab).
It makes sense, in a way, because the tickets are organized by sprints (and Epics can take number of sprints to complete, so no point in assigning a sprint to an epic).

But - if I leave my Epics without a sprint, how do you avoid a situation where you end up with open Epics, and all the tickets under those epics are already closed?

what's the best practice in this scenario?

Thanks

Roy

1 answer

1 accepted

0 votes
Answer accepted
YY Brother
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 18, 2024

Hi @roy adams 

Welcome to our Community.

Do you need to auto close the Epic once all its child issues are closed? If so, I think jira automation will help you with it.

Thanks,

YY哥

roy adams
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!
June 18, 2024

Thank you YY. Closing epics automatically could cause unintended consequences (let's say all child tickets are closed, but the epic should stay open because more tickets are about to be added to it).

To resolve this, I won't assign sprints to Epic, and have it as part of the PI planning process to find open epics with no child tickets and close them. There's room for error in this process (epics get missed and stay open) but it's good enough.

Suggest an answer

Log in or Sign up to answer