プロジェクト

全般

プロフィール

Vote #81859

未完了

Issue copying ignores workflow rules

Admin Redmine さんが3年以上前に追加.

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

0%

予定工数:
category_id:
0
version_id:
0
issue_org_id:
36794
author_id:
399232
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

@Issue.copy@ ignores rules defined by workflow for status @New@ (new issue form).

A simple example.

Let's say we have an issue:

Project: eCookBook
Tracker: Bug
Status: Closed
Category: Print

Create a workflow rule where for tracker @Bug@ and role @Manager@ field @Category@ is read-only on status @New@.

User with given role presses the Copy button. New issue form is shown, as expected by workflow there is no Category field because it is not editable by user.

Press create and see that field Category was succesfully copied even though user can't edit it.

Also steps to reproduce on a test database with loaded fixtures:

  1. Go to Administration - Workflow - Fields permissions
  2. Select role Manager, tracker Bug press edit
  3. Make @Float field@ read-only for status @New@
  4. Log as @jsmith@ and copy issue#1
  5. There is no @Float field@ on form
  6. Save the issue and see that @Float field@ was copied

journals

Patch with fix attachment:"36794.patch"
--------------------------------------------------------------------------------

表示するデータがありません

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

いいね!0