Defect #20257
Read-only essential custom field at the time of ticket editing
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Custom fields | |||
| Target version: | - | |||
| Resolution: | Duplicate | Affected version: | 3.0.0 |
Description
You set required for the custom field X of X tracker.
Set the read-only from the "authority to the field" for the custom field X of X tracker.
When you create a ticket to the new, because the default value is set in the custom field X, you can create a ticket without a problem.
Edit the ticket, when you have selected the X tracker, for the custom field A, to not set a default value, it can not be created ticket.
This is, What specification? Or would bug?
Related issues
History
#1
Updated by Toshi MARUYAMA almost 7 years ago
- Category set to Custom fields
#2
Updated by Toshi MARUYAMA almost 7 years ago
- Subject changed from Read-only essential items at the time of ticket editing to Read-only essential custom field at the time of ticket editing
#3
Updated by Go MAEDA over 5 years ago
- Duplicates Defect #19193: Custom Field definition inconsistency added
#4
Updated by Go MAEDA over 5 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Fixed by #19193 (Redmine 3.1.0).