EPIC's or Versions or multiple projects

[Lyndon Hicks]

I have a large project and the product owner is wanting versioning of epics instead of a long list of epics in the road map. Example Version 1 would have 4 epics Version 2 would have 5 epics etc..

The concern with the long list of epics in the road map is that work within the epics would start to blur and become unmanageable hence the versioning. I am not seeing anything within the help documentation that addresses versioning 

Would the best practice be to create versions with multiple epics within them or create a series of projects within a master project?

We are using SCRUM 

Any suggestions would be most welcome

[Jack Brickey · Accepted solution]

Jira supports versioning by way of a Fix Version(s) field. Generally that is intended to be "past tense" as in the issue was fixed in 1.2, 1.4, 1.5 but often people use for planning purposes. While Epics can be fully contained w/in a release, more often than not an epic spans multiple releases so generally I don't use versions on Epics. However, I don't see why you couldn't add Fix Version to the Epic and do so.

One disclaimer, if you are on cloud using Next-gen the above doesn't apply as versioning isn't yet in NG projects and Epics behave differently in NG as well.