How does your company...

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?

1 answer

1 accepted

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.

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

288 views 38 9
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot