Changing value in automation when I change swimlane?

[Mathieu Cossette]

Is there a way to automate the change of a field when I try to move a card from swimlane?

[John Funk · Accepted solution]

Hi Mathieu,

How are your swimlanes set up? Are they based on a queries or something else? If queries, then you should be able to use Conditions in an automation rule to mimic the Field Value Changed for a card.

[Mathieu Cossette]

Thanks for your response, I have set up my swimlane with JQK where my value of Risk Impact is [Low, Medium, High] and i want to change the value just by draging my card from one lane to the other (just Like status that I already use for probability). I want to be able to drag a card to an other "impact" and that the value is changed when I do that. 

I've tried conditions but I'm not entirely sure what I'm dooing...

[Bill Sheboy]

That will not work as you described...

Imagine creating swim lanes based on a different JQL query, such as based on the Created field and the current date / time.  Dragging a work item would not change when the item was created...or change the current date / time.

And as the JQL for swim lanes could check multiple field values, Jira could not "decide" what values to use for the operation to set them.

[Mathieu Cossette]

Thanks, I was hoping for a built in solution that I didn't know about but you confirm what I suspected.

It's true that in some case it would not react work/react but it could still be available as an option if you configure it correctly (as in my case, I use a single list custom field.)

Thanks guys!

[Bill Sheboy]

Hi @Mathieu Cossette 

Do you mean when a work item transitions status between the board columns (i.e., drag-and-drop left or right direction) or when something else changes?

If it is the status, please try using an automation rule triggered on Work Item Transitioned:

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-transitioned

Kind regards,
Bill

[Prateek]

Use Field-Based Triggers

If your swimlanes are based on a specific field (e.g., “Priority” or “Team”), then:

• Create an automation rule triggered by a change in that field.

• Example: “When ‘Team’ field changes → update ‘Owner’ field” or “Add label X”.

Use Status Transitions (if applicable)

If swimlane movement corresponds with a status change (like moving across columns), you can use:

• Trigger: Issue transitioned

• Then: Edit issue fields or send notifications

Advanced Option: JQL-Based Swimlanes

If your swimlanes are based on JQL filters, you can:

• Monitor the field that drives the JQL condition.

• Trigger automation when that field changes.

So while you can’t automate based on “swimlane movement” directly, you can automate based on the underlying field change that causes the card to appear in a different swimlane.

Let me know what field your swimlanes are based on — I can help you build a custom rule!

[Mathieu Cossette]

Thanks for your responses, Status are already my column in my board. Also , I don't want to change the value of my field for it to change swimlane but the other way around. If I read this correctly {So while you can’t automate based on “swimlane movement” directly} then it's behave as I thought and my idea will not work.

This is a field not in my workflow as it already been used for an other value. (see my answer to John)