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

JIRA Kanban board multiple projects bug

Ytsen Boer, de

Hi, I've come across a bug, probably related to another post on this forum.

I've created a Kanban board based on a saved filter for issues from multiple projects:

assignee = currentUser() and issuetype != Epic and status != Done order by Rank

However, I'm getting this for an issue from one of the projects:

The board is supposed to group by Epics. However, it sorts some of the issues under "Issues without epic". But the issue in that group is itself an epic.

Obviously, when adding more epics, their issues will now be lumped together under "issues without epic".

In the other post I mentioned earlier someone asks to investigate the "issue hierarchy". However, in my project there seems not to be a section "issue hierarchy". Not sure either what I could "fix" there ... ?

Any pointers or workarounds would be greatly appreciated!

Accepted answers

Ytsen Boer, de

So, it turns out that the other project had renamed their Epics into Initiatives and their Stories into Epics.

Thanks for the help, in particular to @Kavitha Chandrasekaran , and sorry for the fuss.

All comments

Kavitha Chandrasekaran

Hi @Ytsen Boer, de

It looks like the sub-task is being grouped under "Issues without an Epic, as sub-tasks do not have parent. If the task associated with that sub-task is in the board, then the sub-task will be grouped under the right Epic.

Hope this helps!

Ytsen Boer, de

Hi, thank you, it is indeed a subtask (however, its parent really is the epic).

But are you suggesting that if I would create a Story under the epic, then things would look differently?

Would you know how to proceed to do that?

Kavitha Chandrasekaran

Hey - Not seen a sub-task directly link to an EPIC :-) in my 10+ years using Jira. But if it did (like your screenshot), it should group under the Epic I would think. Can you go to Project Settings -->Issues-->Types and send the screenshot.

yes, there is another place where the issue hierarchy is set, but we can take a look at what issue types are defined in your project first (like the one below).

Screenshot 2024-06-04 at 9.54.44 PM.png

Kavitha Chandrasekaran

@Ytsen Boer, de You can check the issue hierarchy by going to Jira Settings --> issues-->Issue Types

This is not at Project level but at Jira level setting.

Screenshot 2024-06-04 at 10.02.20 PM.png

Ytsen Boer, de

So, it turns out that the other project had renamed their Epics into Initiatives and their Stories into Epics.

Thanks for the help, in particular to @Kavitha Chandrasekaran , and sorry for the fuss.

Kavitha Chandrasekaran

All good! @Ytsen Boer, de Happy to know root cause was identified and it got resolved.

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

bug