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

Board not filtering by story or epic on bespoke ticket types

philipf

I created a new epic (level 1) and a new story (level-0).

However, when I go into the board and try to sort the board view by epic or stories. The new ticket type appear in 'issues without an epic'. One is an epic so that is silly.

Is this happening because it is no longer named "epic' so the board doesn't know what to look for?

Accepted answers

Trudy P Claspill

Hello @philipf

Are you working with a Team Managed project or a Company Managed project? That information will display at the bottom the the navigation panel on the left.

Are you working with a Kanban board or a Scrum board?

When you say you are "sorting" the board, exactly how are you setting that sort? Are you talking about setting Swimlanes.

When you say you "created a new epic" do you mean you created a new issue of type Epic, or do you mean you created a new issue type, named it "level 1" and added it to the issue hierarchy at the same level as Epic?

If you can provide some screen images to help illustrate your problem, that would be useful.

pfort

Hello,

1. Using a company managed project in cloud version.2

2. Kanban board

3. When i go to board settings, swimlanes, and then select 'base swimlanes on'

4. I created a new level 1 epic called 'legal hold, so now have two epics

- it is this new level one "epic" that doesn't create a swimlane in the kanban board when I set the swimlane to be based one epics.

All comments

Trudy P Claspill

Hello @philipf

Are you working with a Team Managed project or a Company Managed project? That information will display at the bottom the the navigation panel on the left.

Are you working with a Kanban board or a Scrum board?

When you say you are "sorting" the board, exactly how are you setting that sort? Are you talking about setting Swimlanes.

If you can provide some screen images to help illustrate your problem, that would be useful.

pfort

Hello,

1. Using a company managed project in cloud version.2

2. Kanban board

3. When i go to board settings, swimlanes, and then select 'base swimlanes on'

4. I created a new level 1 epic called 'legal hold, so now have two epics

- it is this new level one "epic" that doesn't create a swimlane in the kanban board when I set the swimlane to be based one epics.

Trudy P Claspill

It sounds like you have created a new issue type named "legal hold" and added it to your Issue Type Hierarchy at the same level as the built in issue type Epic. Is that correct?

If so, then the board is currently working as designed.

The Swimlanes Based On Epics option works only with the built-in Epic issue type.

I have not yet found a change request in the public Atlassian backlog about this. You may want to reach out to Atlassian support directly to ask if such a change request exists.

<EDIT>

I did find a change request about supporting multiple issue types at the Epic level:

https://jira.atlassian.com/browse/JRACLOUD-80492

philipf

Thank you,

would this also apply to a story.

So if I created a new level-0 story named 'legal holds' it also wouldn't have the swimlane functionality?

Thank you,

Trudy P Claspill

This limitation applies only issue types that you add to level 1.

When you create new issue types in Jira they are created as either standard issue types (level 0) or subtask issue types (level -1). There is no option to create an issue type that mimics the Epic issue type.

Screenshot 2023-09-25 at 12.29.15 PM.png

Your new issue type for "legal holds" was likely created as a standard issue type.

Adding issue types to Epic and above levels in the Issue Type Hierarchy enables you to use that hierarchy in the Advanced Roadmaps Plans. The new issue types are created as Level 0 issues, but by adding them to other levels in the Issue Type Hierarchy that creates a parent/child hierarchy that AR Plans can visualize. Agile Boards have not been enhanced to leverage the extended hierarchy.

If you remove your "legal holds" issue from Level 1 in the Issue Type Hierarchy and don't add it to any other level explicitly, then it will be treated as and function as a Level 0 standard issue. Note that you will not be able to make other Level 0 issues children of it at that point. You would have to create subtasks to have children under the "legal holds" issues.

When you choose to set your Swimlanes to Stories, that is short hand for setting your Swimlanes to Level 0 issue types.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud