We're thinking about switching to cloud based next-gen projects because we like the simplicity and the road-map tool.
We have a fair amount of different products that we usually divide into separate projects:
WAP (Web App)
NAP (Native App)
HWA (Hardware Product A)
HWB (Hardware Product B)
Because most epics will require work on multiple projects, we want to create a separate epics project just containing the epics. We now would like to add child issues (stories and improvements) from the different projects to the epic.
EPC (Epics Project)
-> EPC-1 (Epic 1)
-> Child Issue 1: WAP-1
-> Child Issue 2: NAP-9
-> Child Issue 3: HWA-3
Is this somehow possible? It seems I can just add issues from the same project to an epic.
Is there a better way to structure projects / labels / epics / issues in jira next-gen?
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events