Kanban Board with Two Issue Types

[Jill Bolger]

Hello, 

Newbie to Jira Admin here.

I have setup a Kanban board for an ongoing project. 

This project has two sub-sections (Mobile App and Web App), to which all issues will fall under one of those headers.

Is there a way I can create two headers for issues on the Kanban board, without creating two boards? Simplicity is key here, so would be ideal to keep everything in one place.

Thanks (in advance) for your insight.

[Trudy Claspill · Accepted solution]

Hello @Jill Bolger 

How are you assigning a value for this "header" to each issue?

Depending on the answer to that, there are a couple of options you can explore.

You can use Quick Filters to set a filter based on that "header" value. When activated, a Quick Filter will hide all the issues that don't match the filters. The issues still exists, they are just hidden from view. Quick Filters can be toggled on and off.

Alternately you might be able to use Swimlanes to group the issues based on the "header" value.

If those suggestions don't address your need, then we'll need more information on how you apply those "header" values to issues.

On a side note, if you are new to Jira you might want to check out the Atlassian University. It provides self-paced classes on a variety of topics related to Atlassian tools. You might benefit from the Jira Fundamentals course.

[Jill Bolger]

Hi @Trudy Claspill - thanks for the guidance. I think swimlanes might be the right fit for me on this one.

I have indeed done the Jira Fundamentals, I found it incredibly valuable. It's a bit challenging to take something from a course and put it into real life in a practical way, though. It's just a matter of working through and doing it myself. When possible, I go back to the course to find an answer, but that is a grind in and of itself, sometimes.

[Raimon Colmenares]

Thanks Trudy, this is very useful.

[Trudy Claspill]

I'm always happy to help. :-)

[Hamza Chundrigar]

Hi @Jill Bolger 

Trudy’s made some great points. Another option that may be worth considering/exploring is making gainful use of components.

Components can be used to organize and filter issues. These are subsections of your jira project (e.g. Mobile App, Web App) and come in handy when you want to generate reports and group issue data contextually.

For more details, feel free to check out the articles below:

•  https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/
• https://www.atlassian.com/blog/jira-software/organize-jira-issues-subcomponents/amp