Recently we decided to try using Epics with Greenhopper, however when we enabled them in Labs and then tried to access our scrum board we got an internal server error.
I found this issue online, and it was said it would be fixed with an update in November. This update seems to have gone through and worked, so I can now enable Epics without getting the internal server error.
However, Epics are all kinds of broken for us. Currently any sub-tasks that have been created since we started using JIRA are showing up in the Epics column on the scrum board. I can't remove them. Plus I went ahead and created an issue type called Epic, which has an Epic Label field and uses the GreenHopper Scrum Issue Type Scheme. If I create an Epic by clicking on the + at the top of the Epics column it doesn't get added as an Epic in this column. If I create a sub-task under any story, it will get added to the Epic column. Very strange.
So, I need to know:
a) How to stop all our sub-tasks appearing as Epics
b) Get Epics working correctly, so that I can create them and then assign stories within them
This is very important, as we want to use a structure of EPIC -> Stories -> Sub-Tasks in future with Scrum.
Thanks in advance for any help!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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