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

How do I automatically change Priority field when moving Kanban issues into new swimlanes?

Brianna Leatham

Accepted answers

Nic Brough -Adaptavist-

You can't move issues between swimlanes.

All comments

Nic Brough -Adaptavist-

You can't move issues between swimlanes.

Brianna Leatham

Thanks for the quick help! New to JIRA.

Nic Brough -Adaptavist-

Welcome!

The reason you can't change things with swimlanes is that they're flexible. It's possible to do things like "swimlane 1 = component is a, b or c" and "swimlane 2 = priority is urgent". There's no way JIRA can know what to change if you moved an issue from one to the other.

You could do it when moving between status though (the status are grouped into the board columns, although a lot of people have a simple "each column is one status" approach). Post-functions on the workflow could set a priority.

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-software

jira-software-cloud

board

kanban