Skip to main content

Move and Duplicate Tasks Across Projects

Learn how to move or duplicate tasks between projects in Allfred. Understand how position mapping works, why it's required when positions differ, and how it keeps assignments and time tracking accurate for both single tasks and bulk actions.

Written by Alexandra Gallisová

Moving or duplicating tasks between projects is a quick way to reuse work without creating everything from scratch. When the target project uses different positions than the original project, Allfred will guide you through a simple position mapping process to keep all assignments and time tracking consistent.

The same behaviour applies whether you are moving or duplicating:

  • a single task

  • multiple tasks using Bulk Actions

How to Move a Task to a Different Project

When moving a task to another project:

  1. Open the task detail view.

  2. Click on the 'Move' button.

  3. Edit the task name if necessary.

  4. Select the target project and budget item for the task.

  5. Update the task description as needed.

  6. Revise details like the deadline, status, or priority for the new project context.

  7. Click 'Move' to complete the action.

The task will open in its new project location, and tracked hours will move with it.

If all positions used on the task exist in the target project, the task is transferred immediately.

However, if one or more positions are missing, Allfred will display a Position mapping required section.

Position Mapping

Each position used on the original task must be matched with an existing position in the destination project.

For every missing position:

  1. Review the Current position.

  2. Select the corresponding New position from the dropdown.

Once every position has been mapped, you can continue with the move or duplication.

Important: Position mapping also updates all related time tracking entries, ensuring that tracked time remains assigned to the correct position in the destination project.

How to Duplicate a Task to a Different Project

When duplicating a task to another project:

  1. Open the task detail view.

  2. Click on the 'Duplicate' button.

  3. Edit the task name if necessary.

  4. Select the target project and the budget item to which the task should be duplicated.

  5. Edit the task description if required.

  6. Decide if you want to include task comments, attachments, and linked tasks.

  7. Adjust details like deadline, status, or priority to fit the new task context.

  8. Click 'Duplicate' to finalize.

Your newly duplicated task will open automatically, but please keep in mind that tracked hours will not be duplicated.

⚠️ NOTE: If all positions used on the task exist in the target project, the task is transferred immediately.

However, if one or more positions are missing, Allfred will display a Position mapping required section.


Move or Duplicate Multiple Tasks (Bulk Actions)

The same logic applies when moving or duplicating multiple tasks at once.

  1. Select the tasks.

  2. Choose Bulk Actions → Move or Bulk Actions → Duplicate.

  3. Select the destination project.

If some positions don't exist in the target project, Allfred will ask you to map them before completing the action.

Only the positions that are missing in the destination project need to be mapped.

Why Is Position Mapping Required?

Projects can have different position structures. For example:

  • Source project contains Backend Developer

  • Target project only contains Programmer

Since the original position doesn't exist in the target project, Allfred needs to know which position should replace it.

This ensures that:

  • task assignments remain valid,

  • tracked hours stay correctly categorised,

  • reporting remains accurate after the move or duplication.

Hourly Rates and Tracked Time Value

When moving or duplicating tasks between projects, keep in mind that the mapped positions may have different hourly rates in the destination project.

If the hourly rate of a mapped position differs from the original project:

  • the tracked hours remain unchanged,

  • but the Tracked Time Value is automatically recalculated using the hourly rate of the destination project.

This ensures that all financial reports, profitability calculations, and work values are consistent with the pricing configured in the target project.

Example:
A task contains 10 tracked hours on a Backend Developer position billed at €80/hour in the original project. If that position is mapped to Programmer in the destination project with an hourly rate of €100/hour, the tracked time value will be recalculated from €800 to €1,000, while the tracked hours remain 10 hours.


Good to know

  • Position mapping is required only when the target project doesn't contain one or more positions used on the task(s).

  • The same mapping workflow is used for both Move and Duplicate.

  • The behaviour is identical for single tasks and Bulk Actions.

  • Time-tracking entries are automatically updated to reflect the newly selected position.

  • If the mapped position has a different hourly rate in the destination project, the Tracked Time Value is recalculated using the destination project's hourly rate, while the tracked hours remain unchanged.

Did this answer your question?