Hi everyone,
I have a scrum project in Jira and I want to create a separate Kanban board to track the progress of some larger chuncks of work independent of our sprints. It would be great if we could see the issues grouped per Epic, but the swimlane by Epic option is not working as expected.
With the option enabled, my board looks like this:
I wasn't expecting the epic to show up as a card on the board, I would like to see it as a foldable section on the board, with the associated stories underneath.
The filter I am using looks as follows:
project = "project1" AND issuetype in (Epic, Story) and summary ~ test ORDER BY Rank ASC
Any help would be strongly appreciated!
Hello Emma,
I have reviewed your affected board configurations, you have created the board with JQL filter and location is set to personal (set to user only).
I created a similar set up on my test project and found that the swimlanes for epic did not work as expected when we used a kanban board and issues are filtered from a team managed project. On the other hand the same was working when the source of issues to the board are from a company managed project.
I have therefore created a potential bug for the same to identify the root cause. I also request you to comment and add yourself as a watcher to get the latest updates on the bug.
Please let me know if this was helpful
Thanks & Regards,
–
NAGABHARANA S
Atlassian Cloud Support
Thank you very much for looking into this! I hope the bug will be resolved soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Emma,
I created a support ticket on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-817731
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Emma Van de Velde and welcome to the Community!
There doesn't seem to be anything wrong with what you are trying to do there. I have noticed the same unexpected behaviour in my own test instance, so checked in directly with Atlassian support about this issue.
I suspect it is a glitch that will be fixed ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for picking it up with support. Would it be possible to let me know if you get any insight in a potential solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my site I am seeing swimlanes by Epics now.
One thing I do notice on your board though, is that your stories don't seem to be linked to epics. Normally, if they are, the Epic lozenge would be displayed on each epic like you can see in this screenshot (the purple boxes on the story cards):
After you verify that and are absolutely sure that your stories are properly linked to Epics that are also on the board, try again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my backlog it looks like this:
So I assume the stories are properly linked to the Epic. However, the board still looks the same for me.
I did notice indeed that the Epic labels are missing on the cards on the Kanban board, but I'm not able to display them (the hide/show epic label action doesn't do anything).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let's wait for what the support ticket leads to, I'd say!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.