By default, Atlas allows to link one Epic upon creation of a project. The real power of linking an Atlas project to a Jira issue would be realised if it is allowed to link it to something higher in hierarchy, i.e.: an issue type "project" or "initiative" that is the parent of a collection of Epics and forms an old-school project.
Otherwise Atlassian is just adding more confusion by now making projects (as managed in Atlas) equivalent to Epics. The risk of it is that reporting on a project will become an exercise of micromanaging which specific tasks have been completed since the previous report.
Hello, we use an issue type called "Parent Epic" which works great at capturing the status of the whole project to sync with Atlas. Parent Epic is the next level above epic in our jira instance.
Hi @Daniel Caballero -- This feature is definitely supported in Atlas + Jira Premium. I use it all the time. But strangely, I can't find the announcement from when Atlassian released it. It doesn't seem to be documented anywhere!
But here are two screenshots from my environment:
We also have an issue type higher than an Epic. When people started using Atlas, they saw documentation from Atlassian indicating that Atlas projects should be linked to Jira Epics.
This is confusing, because it is okay to link to an Initiative (above the Epic), but people were hesitant to do so because they thought they were breaking Atlassian recommendations. The Atlas documentation should be updated so people aren't boxed in.
We already link to a higher issue in the hierarchy... Are you experiencing a problem with doing this? We have an issuetype called 'Deliverable' that our Epics roll up to and it seems to work just fine.
Synching is working and I don't see issues, so is there something missing when you try this?
Hi