Project

General

Profile

Actions

Defect #27110

closed

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

Added by Felix Schäfer about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

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.


Files

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

Updated by Felix Schäfer about 7 years ago

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

Actions #2

Updated by Go MAEDA about 7 years 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.

Actions #3

Updated by Go MAEDA almost 7 years ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed
  • Affected version changed from 3.4.2 to 3.3.5

Committed in the trunk and merged to 3.4-stale and 3.3-stable.
Thank you for sharing the patch.

Actions

Also available in: Atom PDF