One additional note specifically in terms of moving a task to a different section in another project (i.e. a project other than the one where the rule is built): the first rule action that @Arthur_BEGOU showed will do that and is all you need. You might think, “But the task already exists in the other project so the Add to another project action isn’t what I want”. However, the way that rule action works is, if the task already exists in that other project, it will just leave it there but will move it to whatever section is specified in the rule.
The second rule action Arthur showed would move the task in the current project (where the rule lives) but that wasn’t part of your specific use case.
Maybe I’m not following, but I don’t want every task that is added to a section to trigger a movement.
In my Sprint Planning project I have an ‘In sprint’ section.
If I have the rule ‘Task is moved > check if section is in sprint > move or add to project (project = Bugs etc, Section = In sprint)’, it adds every single task that I add to In spring in Sprint Planning to the Bugs > In sprint section, even if the task wasn’t a part of that project already.
I only want a task to be added to Bugs > In sprint it it was already in the Bugs project. So I need a condition like ‘Task is part of project Bugs’ or something.
Ah, you didn’t mention that part. Yeah, there’s no Condition for “task is in Project X”.
The only way I know of to do what you’re wanting is to use a global (i.e. library) custom field (or you could use a tag with a rule in our Flowsana integration) to sync the sections in the two projects.
You’d have a rule in the Sprint Planning project of "If task is moved to section In sprint, set the custom field In sprint to Yes. Then also have a rule in the Bugs project of “If custom field In sprint is set to Yes, move the task to the In sprint section”.
Above I’m illustrating using a dropdown list custom field with only one value of Yes, but for a more general approach you could also use a custom field called something like Stage with values of Planned, In sprint, etc.
On a related note, you might also be interested in upvoting this request: