Next-gen projects from Jira provide a simplified way for administrators and end-users to setup their projects. In classic projects, Jira administrators can configure a project using schemes to map shared objects to their projects. In next-gen projects, much of this configuration can be done by the project owner without the need for to use system-wide types and fields.
Here a few support articles from Atlassian that explain next-gen Jira projects:
- Everything you want to know about next-gen projects in Jira
- Getting started with next-gen projects
- Classic and next-gen project templates in Jira Software Cloud
The Aha! integration with Jira supports next-gen projects, however there are some limitations.
Known limitations with next-gen project integrations
- The Epic link field cannot be mapped, which means that parent/child relationships between epics and stories cannot be synced.
- If you are trying to sync time tracking information, only the Story Point Estimate field can be exposed on a Jira create/edit screen and mapped with Aha!. Meaning, estimates can only be synced if they are in story point units, not time-based units.
- Logged time cannot be synced between the two systems.