プロジェクト

全般

プロフィール

Vote #81272

未完了

Inconsistencies working with workflow permissions

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

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

0%

予定工数:
category_id:
41
version_id:
0
issue_org_id:
34778
author_id:
127719
assigned_to_id:
0
comments:
4
status_id:
9
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
127
ステータス-->[Confirmed]

説明

Found two problems working with setting workflow permissions to read_only:

On Admin > Workflows > Permissions:
when you set tracker_id to "read_only" for the first tracker/status, on a project that has this tracker as the first tracker, you can't chose another tracker when creating a new issue,
when you set subject to "read-only" for the first tracker/status, you can't create a new issue with this tracker, as it it required and has no default.

Editing an issue
after you change from a status that have tracker_id set to "read-only", to another status that doesn't
before you save
when you try to change the tracker to another tracker
the page refreshes and doesn't change the tracker_id

Patches attached:


journals

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Maybe allowing to configure fields permission for new issues (#28150) is a nice solution.
--------------------------------------------------------------------------------


related_issues

relates,Confirmed,29300,New issue can't select read-only tracker
relates,New,28150,Ability to choose Fields permissions for new issue

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

  • カテゴリIssues workflow_41 にセット

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

いいね!0
いいね!0