プロジェクト

全般

プロフィール

Vote #78846

完了

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

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
136
issue_org_id:
27110
author_id:
3866
assigned_to_id:
332
comments:
3
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
131
ステータス-->[Closed]

説明

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.


journals

The attached patch will keep the tracker field in the form if the tracker field has been changed to avoid this problem.
--------------------------------------------------------------------------------
I confirmed the problem and the patch works fine for me.
Setting target version to 3.3.6.
--------------------------------------------------------------------------------
Committed in the trunk and merged to 3.4-stale and 3.3-stable.
Thank you for sharing the patch.
--------------------------------------------------------------------------------

Admin Redmine さんが約4年前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン3.3.6_136 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0