Being able to set rules initiating a specific action (i.e. move a card) in case that something else happens (i.e. if card is past due date) would make Wekan very suitable for several professional use-cases. Implementing this would top existing possibilities that, only Odoo partially covers (and which aren't really present in Trello). Typical use cases:
Recreate a card yearly on 1st June: i.e. company ABC needs to perform periodic maintainance on a machine to adhere to standards.
Send mail if card is moved: i.e. if the above card is recreated, and the safety manger of ABC moves it from TODO to DOING, send automatic maintenance request to company XYZ and a copy to the safety manager.
Create a card if some other card past due date: lets assume the recreated card isn't moved to "DONE" within 15 days. There's a problem that needs to be elevated higher up the food chain. So the rule might create a new card on ABC's production directors' board to figure out what's happening.
... usecases such as this can be quite many as you can surely imagine and could act upon external events (i.e. according to ABC's bank API, the company received $10.000.000 or more --> create a card: "party hard").
There are some ways to approach this issue:
- implement a subset of features directly into Wekan
- bind wekan with another opensource tool (https://github.com/huginn/huginn comes to my mind) and make these two play together smoother then butter (i.e. create rules from within wekan)
Using the 2nd approach make's things a bit more complex and limited by huginn (or similar), but would also help resolve integration tickets such as #1100 . In case someone would pick this up, I'm willing to build a VPS and offer it to the wekan team on which huginn (or anything else) would be preconfigured in case that would be needed/welcomed.
Being able to set rules initiating a specific action (i.e. move a card) in case that something else happens (i.e. if card is past due date) would make Wekan very suitable for several professional use-cases. Implementing this would top existing possibilities that, only Odoo partially covers (and which aren't really present in Trello). Typical use cases:
Recreate a card yearly on 1st June: i.e. company ABC needs to perform periodic maintainance on a machine to adhere to standards.
Send mail if card is moved: i.e. if the above card is recreated, and the safety manger of ABC moves it from TODO to DOING, send automatic maintenance request to company XYZ and a copy to the safety manager.
Create a card if some other card past due date: lets assume the recreated card isn't moved to "DONE" within 15 days. There's a problem that needs to be elevated higher up the food chain. So the rule might create a new card on ABC's production directors' board to figure out what's happening.
... usecases such as this can be quite many as you can surely imagine and could act upon external events (i.e. according to ABC's bank API, the company received $10.000.000 or more --> create a card: "party hard").
There are some ways to approach this issue:
Using the 2nd approach make's things a bit more complex and limited by huginn (or similar), but would also help resolve integration tickets such as #1100 . In case someone would pick this up, I'm willing to build a VPS and offer it to the wekan team on which huginn (or anything else) would be preconfigured in case that would be needed/welcomed.