Best/worst practices question: Is having a dedicated project for Epics a terrible idea?

Rob Horan

For reasons I don't want to go into here, I am considering creating a solution for a customer in which they would have a dedicated project for epics.  Epics would be the only issue type allowed in this project, and creation/editing would be tightly controlled.  Users would have the ability to create stories/tasks/bugs/etc in other projects and link via Epic Link.  Are there any reasons for why this is a terrible idea?

Tom Lister_fo1j4e

Hi @Rob Horan 

I would not say there are any reasons or problems for not doing that. It is common for Epics to span work by multiple teams/projects and they have to reside somewhere. We create epics in a central project and use automation to generate issues in projects owned by different regions. They all see the epic but they don’t see each other’s task progress.