Some card(s)/column(s) sometimes fail(s)

[philschatz]

Some card(s)/column(s) sometimes fail(s)

[janpio]

Ok, while debugging another issue (which looked like #11) I have another combination of failing cards/columns:

If

###### Automation Rules
- `added_label` **wontfix**

is right to

###### Automation Rules
- `accepted_pullrequest`

adding the wontfix label doesn't do anything.

Here I don't see any topical connection, so this doesn't make sense at all.

Is it maybe connected to the fact that the columns is x columns to the right?
What would be the best way to debug this?
Could/shoult the bot maybe add a comment to an issue/PR if moving it fails for whatever reason with some information?

[janpio]

I created a new project board and setup up just 4 columns to test what I wrote in the comment before:

###### Automation Rules
- `new_issue`

###### Automation Rules
- `added_label` **bug**

###### Automation Rules
- `accepted_pullrequest`

###### Automation Rules
- `added_label` **discussion**

per my observation and theory in #17 (comment) after creating a new issue, it should have appeared in column 1. Then adding the bug label should have moved it to column 2. That both worked. Then removing bug and adding discussion should not have moved it to column 4 because of the theorized blocking of accepted_pullrequest. But - the issue moved to column 4 just fine. Toggling the labels between discussion and bug also toggled the issue from col 2 to 4.

So it seems not to be connected to actual content of a column left to it at all.
Which leaves only "too much to the right" of my previous theories.

Strange.

[philschatz]

Cards in columns do not block a card from moving to a column on the right. In general, the only way in which project-bot is aware of the order of columns is that it checks if a GitHub event matches the configuration. If so, it moves the card. And I believe it applies the cards in-order left-to-right and top-to-bottom.

column | column
1      | 3
2      | 4

[janpio]

Hm, I expected so - but still have some automation rules not working sometimes, similar to #11 and the ones documented above of course :/

What would be the best way to debug this?
Any idea what could possibly result in a rule not being executed?