I found your post while checking for duplicates before submitting a similar feature request for GLPI, so I’d like to leave a comment.

I also strongly hope this feature will be implemented in GLPI! (It’s actually surprising that more people haven’t requested it yet.)

In many real-world use cases, we manage our work by boundaries such as “FY2025 Project” or “Version 1.0”. There are many cases where we would like to move existing tasks to a subsequent project, such as “FY2026 Project” or “Version 1.1”.

At the moment, I manually copy and paste dozens of tasks, but realistically, it’s not practical to transfer all the details that way.

For example, in Redmine and similar systems, switching a task’s project can be done very easily. It’s a real shame that this isn’t possible in GLPI’s project module yet. GLPI is a truly excellent piece of software, and I hope to keep using it for a long time—so I sincerely hope this feature can be added in the future!