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; } } }

Story disappears from Sprint when linked to an Epic

Peter Ellis

Hiya,

Not sure if this is a bug or standard behaviour. A Story exists on a sprint board as normal the filter being used is,

project in (ABC, DEF) ORDER BY Rank ASC

If the Story is now linked to an Epic, in project GHI, via an epic link the Story disappears from the current sprint. The Story is still however in the backlog. Is this standard behaviour or a bug?

Accepted answers

Nic Brough -Adaptavist-

Hi Peter,

Could you check the history of the issue? Did anything else change when you added the Epic link?

All comments

Laurie Sciutti

Hi @Peter Ellis ~ by "disappear", do you mean that the sprint field is cleared out or that the Story is no longer visible on your Scrum board? Do you have automation that clears the sprint field or moves the Story to another project? Do you have any quick filters selected to filter the viewed results on your Scrum board?

Peter Ellis

HI Laurie, The Story is no longer visible in the Sprint board. There is no automation or quick filters on the board.

Nic Brough -Adaptavist-

Hi Peter,

Could you check the history of the issue? Did anything else change when you added the Epic link?

Peter Ellis

Epic TVG-2536.png Story TVSEC-124.png Hi Nic, I have attached the history section of the tickets involved. Nothing else changed when the epic link was added.

Nic Brough -Adaptavist-

Given your board filter, and that nothing else on the issue has changed according to the history, I am pretty much stuck.

I think this needs to go to Atlassian support.

There is one other question - do you take Epics into sprints? If you do, is the Epic you linked to possibly in another sprint? I don't believe that should have any effect, and will have nothing to do with this problem, but I would add the answer to the support call.

Peter Ellis

Hi @Nic Brough -Adaptavist- Contacted Atlassian and it turns out to be a simple fix. The swimlane the board was using was sorted by Epic. The issue was linked to an Epic not in the filter so it disappeared.

The solution was to either include the Epic's project in the main filter or change the swimlane. The user changed the swimlane to be sorted by Assignee and that fixed the problem.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server