Keep attributes when moving task to project

[mykappa]

My actions before raising this issue

• Read/searched the docs
• Searched past issues
• Searched google

Suppose you have a project and a separate task. Both have exactly the same labels with the same attribute definitions. When you move the task to the project, all attributes are reset, as is also specified in the tasks page documentation. What is the reason for this? This should not happen. At least the attributes of the original task should be kept or a warning should be issued.

Steps to Reproduce (for bugs)

1. create task with label attributes
2. change the attributes
3. move task to existing project with the same exact label and attribute definitions
4. undesired result: attributes are reset, even in the original task

Expected Behaviour

When moving a task to a project with exactly the same name and attribute definitions, the attributes should be kept as they are and not reset. It looks like such a feature is planned. However, the corresponding checkmarks when moving the task are always grayed out.

Current Behaviour

The attributes are also reset in the original task. All previously performed work to set attributes is lost.

Possible Solution

• At the very least, a warning should be issued alerting the user to the resetting of the attributes in the original task
• If resetting is unavoidable, create a copy of the task so that at least the original attributes are preserved
• Even better: the attributes are taken over as they are from the task

Context

After setting attributes in a task on a server, I made a backup copy of the task and imported it to another machine. When I move the task to the project, all the attributes that I spent hours setting correctly are lost.

Your Environment

• Git hash commit (git log -1): d0c7aa2
• Docker version docker version (e.g. Docker 17.0.05): Docker 20.10.23
• Are you using Docker Swarm or Kubernetes?: no
• Operating System and version (e.g. Linux, Windows, MacOS): Windows Server 2022 Standard 10.020348 Build 20348
• Code example or link to GitHub repo or gist to reproduce problem: -
• Other diagnostic information / logs: -

[bsekachev]

Should be fixed by this PR #5764