Project

General

Profile

Actions

Defect #34778

open

Inconsistencies working with workflow permissions

Added by Frederico Camara about 3 years ago. Updated about 2 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Issues workflow
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

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:


Files


Related issues

Related to Redmine - Defect #29300: New issue can't select read-only trackerConfirmed

Actions
Related to Redmine - Feature #28150: Ability to choose Fields permissions for new issueNew

Actions
Actions #1

Updated by Go MAEDA about 3 years ago

  • Category set to Issues workflow
Actions #2

Updated by Go MAEDA about 2 years ago

  • Related to Defect #29300: New issue can't select read-only tracker added
Actions #3

Updated by Go MAEDA about 2 years ago

  • Related to Feature #28150: Ability to choose Fields permissions for new issue added
Actions #4

Updated by Go MAEDA about 2 years ago

  • Status changed from New to Confirmed

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

Actions

Also available in: Atom PDF