Condensing Issues in Epics

[corey_rotterman]

For the project that I manage in JIRA, we use "Epics" to designate particular pieces of equipment in the laboratory spaces. Under each "Epic", there is an option to "create issue in Epic" and they will show up in the column labeled as "# Issues in this Epic" (# signifying how many issues are currently there). Image below is an example (portions redacted for security reasons).

My concern with how this column is organized is that I do not know if you can condense those to folders or some other type of squished format. Some "Epics" will only get larger over the next month.

[Petter Gonçalves]

Hello Corey,

I understand that you would like to group the issues under an Epic by date or other parameters in order to keep the Issues in this Epic list manageable and readable, without having a huge list of issues under each Epic. Is that correct?

If I've understood it properly, I think you can change the issue-type of your items from Stories to Sub-tasks and use Stories to categorize your items, adding those sub-tasks under Stories defining the way you would like it to be Split.

Basically, you would add one more hierarchy level to your current scenario:

Epics > Stories > Sub-task

And you would use the Stories as "Folders" linked to Epics, and add your items (Sub-tasks) to the Stories based on which criteria you think should be better (Date, kind of equipment, etc).

Please, let me know if I made myself clear and if this scenario would work for you.