I would love to have some Column-Options - as foundation to automate things with cards.

I've read "here and there" that things wanted, like add special tag if card is moved to column x (e.g done tag`), archive the card, set new due-date, etc.

It seems, that those ideas are often undermined by overthinking to much in the beginning. (my opinion)
Caused of this, I would suggest do use KISS principle - keep it stupid simple at the beginning.

I would like to suggest to start it on a very base level and first implement a kind of foundational concept, that allow the idea to grow later on.

Here is my Idea, how to start.

1. Each Column should get an "Setting" area

2. in this setting-area, user can control what happen with cards inside this area:

   Triggers to start action with a card:
   If card is...
   a) moved into this column
   b) created in this column
   c) moved outside of this column

   2 Base functionalities for the beginning:
   a) CHECK if Card has Tag x, SET IT, or REMOVE IT
   b) CHECK if Card has due-date, - SET IT or REMOVE IT

3. Each column-setting can have
   a) NtoN rules for Tags
   b) 1 rule for due-date

4. Rule-Setting for column as simple as : Choose Trigger, choose action
   Examples:

   • Trigger = Card moved into Column, ACTION = SET due-date to choosen value (e.g. today)
   • Trigger = Card moved outside Column, ACTION = REMOVE Due-Date
   • Trigger = Card moved outside Column, ACTION = ADD Tag done

What do you think of this?