Deal with projects that have numerous tasks using Greenhopper? For example, to spin up a new client, there are a half-dozen tasks spread across numerous groups (infrastruture, security, software, etc.)
We've been using sub-tasks, but it's not pleasant because you can't prioritize subtasks outside of the master task and the assumption is that they all finish in the same sprint/iteration - which is invalid. we looked at using Epics, but can't figure out how this differs from any other issue type. Is there any way to set up a chronologically oriented list of tasks to be performed on a single master JIRA issue without having the sub-task problem show up?
