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?
Currently issues don't have a proper hierachy besides subtasks. Epics use issue links and that's the best available. Since you are on OnDemand, unfortunately there isn't too much that can be done. If you had your own hosted instance of JIRA you could look at the Structure plugin to possibly solve your needs. It can sync with GreenHopper's ranks.
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs