nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Epic showing in two spaces

deseymour

For some reason, when I look at two of my Spaces, they both have the same Epics (same numbers, names, etc.). However, if I then click on the Epic, it shows me that Epic under the correct Space. These should only be under one of the Spaces...how do I get them off the other Space? I don't even understand how this is possible...Let me know what else you need to help answer the question.

Accepted answers

deseymour

Oh my gosh! I just cleared out a filter and now it's fine. I have no idea what I did, but now it's working...

All comments

deseymour

Oh my gosh! I just cleared out a filter and now it's fine. I have no idea what I did, but now it's working...

John Funk

Hi @deseymour

I suspect you were looking at a board - is that correct? A board can show work items from multiple spaces on it. However, the Epic itself can only be created against a single space.

BUT, an Epic can have children from multiple spaces.

deseymour

No, actually I was looking at the space itself, but for some reason, there was a filter that was pulling in epics from a different space. It was very weird. Who knows what I did...

John Funk

Please reply inline to the thread so users can follow the conversation.

Where exactly were you looking in the Space?

deseymour

In the All Work view.

John Funk

Okay, that view is not unique to a single space.

Ariel Yadin _ Bazz OKR

Hey @deseymour, this is a really common pain point, and it usually comes down to one thing: Epics don't belong to a Space, they belong to a goal. A few things that helped us get this straight:

Epics are delivery containers, not org chart boxes. If your Epic spans two teams, that's fine. That's actually the point.
The confusion usually starts when Spaces are set up by team instead of by product area. Teams then fight over where the Epic 'lives' instead of focusing on what it delivers.
Define Epic scope by outcome, not by who does the work. Ask: What's the smallest shippable thing that moves a metric? That's your Epic boundary.

The deeper issue I see here is that without a clear line from Epic → goal, Epics sprawl. We ran into this a lot before we started anchoring Epics directly to OKRs. We actually built Bazz OKR partly to solve this for ourselves, connecting Jira Epics to key results so the scoping question almost answers itself.

But even without tooling: write the OKR first, then ask 'what Epics do we need to hit this KR?' That direction of thinking clears up the scoping confusion fast.

Happy to dig into your specific setup if you want to share more about how your Spaces are structured.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud