Defect #12954: Required field can't be read-only - Redmine

Actions

Copy link

Defect #12954

closed

Required field can't be read-only

Added by Daniel Felix about 11 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Issues workflow

Target version:

Start date:

Due date:

% Done:

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:

Set custom field as required
Define field as read-only in workflow
Try to add issue, as you could see the field isn't displayed in the form but is checked in the required process

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

Actions

Copy link

Updated by Daniel Felix about 11 years ago

Description updated (diff)

Actions

Copy link

Updated by Daniel Felix about 11 years ago

Description updated (diff)

Actions

Copy link

Updated by Daniel Felix over 10 years ago

Affected version (unused) changed from 2.2.2 to 2.3.2
Affected version changed from 2.2.2 to 2.3.2

I can reproduce this, even with the current release or with 2.3.2-devel (r12012).

It would be good to prevent setting a field to "hidden", if it is a required field. Or on the other hand, the field should be only required if it is visible to the user.

Actions

Copy link