Jira - forever / neverending Epics for support topics

MarcSch

We are a team responsible for administering Jira (which is our "product") including creating new Jira projects (software or service projects as "real" projects) and supporting or improving internal Jira functionality.

For the "real" projects we create single epics, which is fine as someday they come to an end. To organize word in Jira especially in sprint planning and plan view we have support epics, e. g. "Administration/support Jira" (as well as Confluence) which is sort of a neverending epic.

Would be interesting to hear how you work with support topics that never come to an end.

• neverending epics?
• ending epics for time boxes (e. g. Support 2020, Support 2021...)?
• other ways?

Ravi Sagar _Sparxsys_

Hi @MarcSch 

So your support tickets are organised under epics?

If you have ongoing work or maintenance or small changes to support a product then these can be just standard task (or any other issue type) under a project. Use fields like components to further classify those activities.

Epics can still be created for Quarters but never ending epics might not be a good idea. Although Jira won't stop you from doing it.

For instance if your teams follow sprints then you can create some placeholder epics for each quarter and then add those support tasks under it. This will help stakeholders in reporting when they look at rolled up view of the plan and progress.

I hope it helps.

Ravi