LGPL-3 · Version 18.0.1.1.0

Task Merge

Merge tasks by moving their content onto the kept task instead of stranding it.

Video · Task Merge · 0:59
Two tasks ticked and the merge action: the content moves before the other is archived
Two tasks ticked and the merge action: the content moves before the other is archived

Two people open the same task two days apart. One gets archived, and everything it carried goes with it: the conversation, the attachments, the hours logged on it.

This module moves the content before archiving. The message thread, the activities, the followers, the attachments, the hours and the dependencies are reassigned to the task you keep, and the others are archived, empty.

The hours matter most: they are billable, they feed the hour bank and the project's profitability. An hour trapped in an archived task is neither lost nor visible, which is the worst of the two.

⚠️ Source tasks are archived, never deleted. Their number stays valid and an old reference still leads somewhere, because a dead link in last year's email cannot be explained away.

Comparable to Zendesk ticket merge, for your Odoo tasks

bf_project_merge · Version 18.0.1.1.0 · Guide chapter · View the source · See it in the catalogue

The 97 other applications

Shall we look at your case together?

Tell us what you run today. We will tell you honestly whether Symbifox helps or not.

Keep in touch

The catalog grows almost every month.

What gets added, what we learn deploying it, and nothing else. You leave whenever you want.

One confirmation email, and nothing before you follow its link. Then 10 welcome emails, one a week, then the updates. No tracker, no resale.