jchuet any by 'for now' you mean 'for_ever'. It sad to notice, team, that making instruments for agile, not agile at all.

Epics were released as part of GreenHopper 4.1, they have recently been improved with the release of GreenHopper 4.3.

Hi Andres,

I think you will love this feature request: GHS-706
We are just awaiting for JIRA 4.0 to come out to be able to support it.

Cheers,

Actually this is how we implement Goals (using links). We prefer to implement Epics as a series of sprints (epics are master versions of sprints). I think this fits better in my understanding of Scrum. I think Goals are temporary and are somehow a parent of Stories (especially before you define all the stories). Where as Epics seem time-boxed to me, like sprints.

To round it out, I think Themes are best implemented as a hierarchy of components.

Unfortunately JIRA supports as for now only one level of sub-tasks.
You can vote on the improvement ~ Sub-issues should be able to contain their own sub-issues
here: http://jira.atlassian.com/browse/JRA-4446

A workaround (that we use) is to have a link type called "Is an epic of" ---- "Is a Story of"
It works kinda ok and the hiearchy plugin helps us a ton.

We chose to use the link at the Epic level since the subtasks are much more useful for us on the ongoing progress for the tranking purposes and the TaskBoard visibility.

Cheers,

We are using parent issues as "sub-"epics and subtasks for stories. We also have items unrelated to our sub-epics in our sprints, and the ability to mix-and-match the priorities of subtasks and other issues would be very beneficial.

You should use the subtasks Murali.
They are very well integrated in JIRA and GreenHopper.

So create a Story then let your engineering create the subtasks.
Estimate your Story with Story points
estimate your subtasks in hours

Cheers,