Will there be a way to link more than one EPIC to an Atlas Project?

[Monty Bhatia]

We modelled JIRA where there is a project reflecting each business unit.

Each business unit may come together and work on one project together; while doing their own work in their own project space.

Is there a way to link more than one epic to an atlas project?  Of course we wouldnt sync project or epic titles as a result.

This allows Atlas to reference > 1 epic, and each epic to reference the one atlas project (and corresponding goals).

I know that we can add related links, but I'm wondering if there is a way to create one atlas project to reflect multiple epics.  This would be a great way to provide overall project updates across multiple teams.

Thanks.

[Niraj Patil]

Hi, @Monty Bhatia , thanks for your feedback. We're currently looking into supporting adding multiple epics to an Atlas project but we don't quite have a timeframe on when we'll actively work on it. We hear feedback on this often and as soon as we begin work on this, we'll let you know.

[Monty Bhatia]

Thank you @Niraj Patil hoping to see it implemented.

[Matt Lane]

Thanks for asking the question @Monty Bhatia , and thanks for the response on this @Niraj Patil  !  We really would like to have this (1 to many) functionality to get best value out of how we'd like to use Atlas.

[Jo-Lee Bertrand]

Also voting for this!

[Bruno]

+1 for multiple epics support!

[Kieron Smith]

Yes, +1.

This is definitely an issue for Atlas adoption.  I fail to see what it really offers us over epics themselves.

Epics have a description, comments, a list of tickets, and even a progress meter.  Why do we need Atlas if projects can't bridge multiple epics.

[Jason Amerine]

Yes, +1 on this feature.

[Lewis Baker]

Yes, +1 on this feature.

[Nicola Tesser]

+1 on this feature

[JCameron]

I was really surprised that this wasn't done in the initial implementation. The concept of the tool makes a lot of sense, but this limitation breaks that concept by forcing either a very specific Jira usage and company operational workflow, or by making me not bother linking up projects themselves to the Jira side of things. At least on the Jira side we can link higher level issue types that "live" above Epics, even if those are primarily used for organizational purposes and not actual tasking.

[Bryan Darr]

Is there a jira.atlassian.com issue we can follow for this?

[darntough]

I am also stuck on being able to leverage this tool without tracking against multiple Epics. I would love to hear more on where this feature sits on the Atlas roadmap.

[Parker Mosman]

+1

[Christine Houlding]

Loved the idea of Atlas and got really excited about using it, until I saw I can only link 1 Epic. This simply wouldn't work for us as a project is made up of multiple Epics.  I'm hoping this enhancement will follow soon!

[Mattias Ahnberg]

@Niraj Patil any updates on this one? It is still a massive blocker from what could otherwise be a useful tool for us to use more widely.

[VP]

I agree. There must be a way to link more than 1 epic. We experimented with "Initiative" type in Jira, but that didn't spinoff quite well.

[Jessica Hollander]

This is a blocker for my team to use Atlas as a way to understand our deliveries

[Ben_LeBrocq]

+1 we are unable to use this feature we we need a one-to-many project-to-epic relationship!

[Vladimir Petrović]

@Niraj Patil, is there any news about this feature, when this will be available? Or did you maybe find out some workaround?

Thanks in advance for your feedback. 

[Vladimir Petrović]

I found a workaround. You can create a custom text box field and simply copy and paste as many epic links as you need. However, the downside is that you will not get hyperlinks, just plain text, which you can open in another browser tab afterward.

[Jo-Lee Bertrand]

Only 1 epic is the reason I can no longer use Atlas. - Sorry, this is not an answer but I only seem to be able to edit and not delete. 

[_jonny]

Atlas needs to be able to connect to a Project or an Epic.  Not just an Epic.  :(

[Spencer Kotowick]

+1

What's the point of using projects if it only has a 1:1 mapping to Epics. 

Mind's well just use epics then.

[Thorben Röder]

+1

[Scott Jackson]

Is there a ticket to track this feature request? Definitely +1000 this.

[Kristen]

Atlas is unusable to me at this time, since i have multiple teams and epics that need to go into one goal.  I cannot do this one by one or it's a waste of my time, and my company's money.  I need to be able to set this up quickly and track against it, as a program manager. 

[Ananth Subramanian]

support this feature

[Mirthe]

Any update on this?

[Dragomir Grigorov]

I have been trying to use Atlassian projects for a while for project updates, but having separate projects for each epic is not working for me at all.

I created a brand new project in Jira for one of our projects.

Our dev team is scheduled to work on this project for seven 2-week-long sprints. We have several epics hosting the main features that need to be built, but I would like to use one project with a roadmap and updates on the milestones. Having the option to link only one epic to one project forces me to create a separate project for each epic, even though all of the epics will be built by the same team in one project.

I also do not like the way Confluence is handling the product requirements pages. Each page has its own roadmap macro and is treated as a separate project instead of sharing some elements of the space / (project) they are part of.

This approach may work in really big companies where many dedicated teams work on specific projects, but we have one team of 8-12 people building all the features for a project.

I will give it a try for some additional time, but creating separate projects in Atlassian for each epic feels like creating a brand new project in Jira for each epic, and I really can’t see the value in it.