The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Stories from external epics disappear in swimlanes

Wouter de Winte
Wouter de Winter
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
October 8, 2013

We have put some stories in our sprint that are connected to epics from a different project. This project belongs to a different team that has it's own scum board.

In the work mode when we select "swimlanes by epic" these stories disappear. They also do not show under "issues without epics". This could make sense because they ARE connected to an epic, but not an epic in this board/project.

Is there a known workaround or can we consider this a bug? Thanks for your help!

Watch
Like Be the first to like this
701 views

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Dan Straw
Dan Straw
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
October 21, 2014

I have spoken to Atlassian about this via support, and they have confirmed this is a bug.  You can follow the progress via https://jira.atlassian.com/browse/GHS-11318

Reply
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security