Folders within epics and Epic extension automation
I need to track business Epics, but these are usually large and I like to break them down into smaller-sub-epics to deliver and track (via multiple releases). Jira doesn't support Epics with Epics (unbelievable really) and I need to work at ira as well as structure level so I create folders in structure under the main epic to perform this partitioning. Each Jira story is still linked to the main epic so I can use Epic reporting in main Jira, but it does mean that I can now track sub-epics at the folder level in structure too. Unfortunately this means that I can use the Epic extension automation because it doesn't understand the folders. Because the stories are under the folders not directly under the epic, the automation doesn't realise and creates duplicates under the epic. I guess this is more of a bug than a feature request.
analysis — see comments
Thanks for describing your case. This is a known limitation in the current feature set and we're thinking about how to improve it in the best way. Automation is already quite complicated and we're trying to contain the complexity.
With the current functionality, there are some workarounds that can be done. For example, one could use a grouper after the extender, and group by Label or a custom field, adding another level between Epics and Stories. Stories will still be attached to epics without duplicates. Using Labels has an additional benefit of allowing multiple labels per issue.