I will file a bug report but just to alert anyone here in case it was not an isolated case.
To give you some context, today we were working on sorting lists. For nested cases, we use List Shifter plugin, so it is not something new, we use this in multiple places. So we created a new branch to implement this in some additional columns.
Then we noticed that some sorting workflows were not working as they should. Even though they were just copied from one column to another along with the target element using the “Copy with workflows” action.
No issues in the issue checker, after all they were in the same context of use, using the same references after copied.
The problem is that they weren’t sorting as they should, some really weird actions were happening, they were not triggering on the final event. Ok, could it be a problem with the plugin? A problem with the settings? A lost workflow there doing something it shouldn’t? It could… but it wasn’t.
And now comes the weird part. In the old branch everything worked perfectly.
And the weirdest part yet. In the problematic branch, I simply copied the workflow linked to the element, yes… I simply copied the workflow. I deactivated the old one and everything started working normally with the new copied workflow (without any changes).
The question is, what happened in this case? Why did the copy solve the problem even though no changes were made? Can we be sure that using the “Copy with workflows” action is not causing silent problems in the application, in critical processes?
So if something that should work seems to be bugged in your app and you’re struggling to figure it out, after using the “Copy with workflows” action, check if that’s not the case for you too and report the bug.