Defect #27110

Changing the tracker to a tracker with the tracker field set to read-only won't work

Added by Felix Schäfer about 1 month ago. Updated about 1 month ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:3.3.6
Resolution: Affected version:3.4.2


When a tracker has the tracker field set to read-only in the workflow permissions, it is not possible to change to that tracker. When in the issue edit form the tracker field is changed to the tracker with the tracker field set to read-only, the form is reloaded but without the tracker field (as it is read-only). Submitting this form doesn't include the tracker, thus the tracker is not changed.

Additionally, when the issue edit form is reloaded again, for example for a status change, the form is reloaded to the original tracker and changes in fields active in the target tracker but not active in the original tracker will be lost.

27110.patch Magnifier (717 Bytes) Felix Schäfer, 2017-10-02 11:39


#1 Updated by Felix Schäfer about 1 month ago

The attached patch will keep the tracker field in the form if the tracker field has been changed to avoid this problem.

#2 Updated by Go MAEDA about 1 month ago

  • Category set to Issues
  • Target version set to 3.3.6

I confirmed the problem and the patch works fine for me.
Setting target version to 3.3.6.

Also available in: Atom PDF