Project

General

Profile

Actions
Copy link

Defect #12954

closed

Required field can't be read-only

Added by Daniel Felix almost 12 years ago. Updated almost 8 years ago.

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

0%

Estimated time:
Resolution:
Duplicate
Affected version:
2.3.2

Description

Hi,

I've encountered some bug, which prevents the creation of a new issue.

Maybe this is solved by commiting #12005, but in the current trunk and Redmine 2.2.2 this bug is reproduceable.

Ways to reproduce this error:
  1. Set custom field as required
    custom field is set to required
  2. Define field as read-only in workflow
    workflow sets field to read-only
  3. Try to add issue, as you could see the field isn't displayed in the form but is checked in the required process
    configuration raises error

Maybe this one is related with #12856, which hasn't any relation to custom fields, but the result seems to be the same.

Some suggestion to solve this:
Commit patch from #12005, remove required checkbox from custom fields, set currently required fields to "required" in all workflows. This way there is no way to set a field as read-only and required.

Best regards,
Daniel

Files

Download all files
custom_field_required.png (18.7 KB) custom_field_required.png custom field is set to required Daniel Felix, 2013-01-23 10:32
workflow_read_only.png (27.9 KB) workflow_read_only.png workflow sets field to read-only Daniel Felix, 2013-01-23 10:32
failure_in_issues.png (40 KB) failure_in_issues.png configuration raises error Daniel Felix, 2013-01-23 10:32

Related issues

Related to Redmine - Feature #12005: Mightful workflow field enhancement: hideNew

Actions
Related to Redmine - Defect #12856: Required field Category cannot be edited by Non Member user when adding ticketNeeds feedback

Actions
Is duplicate of Redmine - Defect #19193: Custom Field definition inconsistencyNew

Actions
Actions
Copy link

Also available in: Atom PDF