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 Backlog: Create issue not setting component based on board

Rob Shaw_gf4w7x

Under a board backlog the inline create issue is not setting component based on the board filter.

For other boards (and this one until last week) creating an issue from the backlog would apply the right componenet values so the issue would appear in the backlog. For some reason this board stopped behaving this way.

Checked Filter
Re-indexed Project
Board is single project
Checked board setting to ensure columns had right values

All other boards in the project are behaving as expected.

I am Stumped?

Accepted answers

All comments

Gaston Valente_dzz4x1

Robert, are you using scrum or kanban?

The filter has one o more components?

Rob Shaw_gf4w7x

Kanban & the Board Filter has a single component

Alexander Kern

Robert and Gaston

I have the same problem. Until recently our Kanban Board behaved as expected (values for set quick filters were added to new stories).

Now none of the quick filters set values.

Have you found a solution for this?

Rick Carini_05ylai

Was a solution or a Bug opened regarding this?

We are also seeing this problem with every Kanban board that is being generated from a Filter with component selected.

Thanks!

Rick

Gaston Valente_dzz4x1

Rick,

The only way i was able to create an issue with the correct component selected is by using the create issue option at the end of the backlog task list.

it seems that the create window is not linked in any way with the context of the screen, i don't know if it's a bug or by design.

from my point of view, it is ok the current behaviour but you can submit a feature request and let atlassian and the community decide

Rick Carini_05ylai

Thanks, @Gaston Valente, but that is where it is not working for us. We have to manually enter in the Component after we have used the Create issue option at the bottom of the backlog task list.

Evangelos Vrocharis

For everyone else that is looking for what is causing this here: https://jira.atlassian.com/browse/JSWSERVER-14728

It has to do with a component name not being unique, i.e. other projects having similarly named components.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software