We've been running multiple projects for multiple "project teams" all under one large project umbrella. We've discovered that epics are a nice way to link that work across project teams together, but several issues have come up as a result. Epics themselves live in yet a third project, for management and prioritization. I'm hoping someone here can help us sort out what we need to do.
Is it possible that these are addressed in a later version?
BTW, we're running version 4.4.1 of GreenHopper, and 4.1.1 of JIRA.
You would need to upgrade to at least JIRA 4.4.3 and GreenHopper 5.8 in order to use the Rapid Boards. That's when they were first made available.
If you are going to upgrade, I'd probably recommend moving to JIRA 5.1 and GH 6 though after testing new features in your environment. Lots of improvements across the board in both.
Yes, we want to upgrade. It just turns out that the upgrade is likely non-trivial for us, spinning up into another large project that doesn't really get the answer for us immediately. Thanks though. I have access to another JIRA instance that is on 5.1 (hosted) that I can experient with. I'll have a look at rapid boards there as proof-of-concept.
I have similar requirement as Paul has. I have an Epic with several related Issues across different Projects. Can Epic duration be viewed as sum of 'related' Issues duration? Please note that Issues under an Epic are not necessarily sub-tasks under the same Epic. Instead Issues are spread across projects and are linked to Epic. I am using JIRA + Agile +Gantt Chart plugin.
I have similar requirement as you have...Paul . I have an Epic with several related Issues across different Projects. Can Epic duration be viewed as sum of 'related' Issues duration? Please note that Issues under an Epic are not necessarily sub-tasks under the same Epic. Instead Issues are spread across projects and are linked to Epic. I am using JIRA + Agile +Gantt Chart plugin. Any ideas as to how to resolve this?
This is the only way I have been able to roll up status of an Epic across multiple projects. Perhaps it will be useful to you.
Obviously, you will need create/view/edit privileges in all 3 projects.
The trick, here, is that you must maintain the hierarchical relationship between the Epic and its children. If Projects B and C "Move" their User Stories to Epics the parent-child relationship is lost.
If anyone has found a different method that works I would love to hear about it.
Have a great day!
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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