No, because a swimlane is a grouping selected by data on the issues, and there's no way JIRA can know what moving between swimlanes might be doing in most cases. It's ok for the clear simple standard ones (e.g. change the story or assignee it belongs to), but as soon as any clever filters are used, you need rules which can't be fixed.
Think of a simple example of two swimlanes - one is "priority = high" and the other "colour = blue". What do you need to change and what should you change if a user moves an issue from one lane to the other?
I have requirement and need you help.
We have a sprint board and we have stories and Subtask for those one. Lets says if have a stories DDD and Subtask below it are 1- Subtask1 , 2 -Subtask 2 etc.
When Dev team work on it, only Subtask move from one Column to another one, but not the stories
is there Anyway i can only have stories only moving from one column to another in swimlane ?
There is one non-standart easy way that can give you 2 easily controllable swimlanes - by misusing the Flag capability and setting swimlanes by queries. Then you can get two lanes - one with filter "Flagged is not empty" and second without any. Works as you need - not via drag and drop, but via right-click and set/remove flag.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events