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

Can I get a sub-bug to show in a different swimlane from the parent ticket

Jonny_b0juj7

Before starting I'll explain the way the board is setup as you will need to know this to make sense of my question

1) I have a front end seimlane and a separate backend swimlane

2) Any sub-bugs that come out of the parent tickets show on the board and move separately across the board parent ticket

----------

I have a front end parent ticket the team are working from.

A sub-bug have come out of it. It has been deemed as a backend issue.

I would like the sub-bug that is a backend bug to show in the backend swimlane and NOT the front end swimlane so it is clear who can pick this up

Is there a way I can get JUST the Backend sub-bug to appear in the backend swimlane. Currently it just shows in front end as that is where the parent ticket is sitting.

Thanks in advance

Accepted answers

All comments

Stefan Salzl

Hi @Jonny

How dou you distinguish between frontend and backend in your board? what are your swimlanes filter for?

Could you mabe show a screenshot of your board as well as your board-swimlane settings?

Best
Stefan

Jonny_b0juj7

Hi Stefan,

They settings are set as:

project = xyz AND issuetype in ("Frontend Bug", "Frontend Story", "Frontend Task", "Sub-task", "Bug (Sub-task)")

project = xyz AND issuetype in ("Backend Bug", "Backend Story", "Backend Task", "Bug (Sub-task)")

I've tried adding in 'OR labels = BE' to the backend filters but no luck.

Stefan Salzl

You do have seperate issue type for backend as well as frontend? imho this makes your life in jira a lot more complicated and if I my leave my 2 cents: there are way better approaches / best practices. Do you use components?

Anyways.....where does your issue appear when you add the OR condition with label = BE ?

I tried to reproduce this on my site and I get this working with an OR clause (see screenshots)

Jonny_b0juj7

We often have BE and FE work with the same release and this way it keeps it separate as to who needs to concentrate on what. Always happy to hear other people's 2 cents though! We don't use components.

When I have 'OR labels = BE' nothing changes at all. The sub-bug stays in the front end swimlane

------

project = xyz AND issuetype in ("Backend Bug", "Backend Story", "Backend Task", "Bug (Sub-task)") OR labels = BE

Welcome!

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

Quick Links

Find more posts tagged with

jira

swimlane