We have built up a hierachy of issues types "Feature", "User Story" and "Story Task" - with custom coding for automatic issue links, status synchronization, custom field inheritance, effort accumulation and reporting. 2,000 users wordwide.

An issue type "Epic" would break our complete logic and infrastructure. therefore we need to be sure, that GreenHopper remains fully functional and consistent without issue type "Epic".

The UI must not have any references to "Epic" in this case.