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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs