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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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